Running multiple tests to see if your Salesforce org is behaving as you expect is traditionally a manual regression test. With Gearset’s Automated Testing, you can instead schedule multiple UI tests to run automatically.
A test job is a configuration in Gearset that groups a set of UI tests together, defines when they should run, and executes them against a selected Salesforce org. It acts as the mechanism for running your regression suite on a schedule or on demand
Follow these steps, as a tutorial, to create your first Gearset test job by creating a new test job, schedule it, run it and see the results.
Before creating a test tob, you need at least one saved UI test. If you haven’t done this yet, follow our “Creating your first UI Test” guide.
Create a new test job
In Gearset, open
Automated Testing -> UI Testingfrom the main menu.Click New test job.
Fill in the job details
In the Job details step:
Enter a name, for example Core Workflows.
Select the Salesforce Organization you want to run your tests on.
You can also choose how often the job should run automatically:
Daily → select a time.
Weekly → select a day and time.
Click Next.
Select what tests you'd like to run. You can choose all tests to run, or choose a folder containing tests you've built and curated for this regression suite.
Click Next.
Choose how often you'd like to be notified about your test results.
Click Save.
Run your test job manually (first run)
For the first run, you’ll want to trigger the job manually since there won’t be any run history yet. On the test jobs page, click your test's job row to open the side panel. This panel shows the next scheduled run, but you can run it immediately.
View results and run history
Once the test job finishes:
Click your test job again to reopen the side panel.
From here, you can review:
The Salesforce organization the tests are running against
The next scheduled run time
A run history for each execution, showing how many tests passed or failed
Select the most recent entry in the run history to view detailed results. You’ll be able to see every test that ran, including:
Whether it passed or failed
How long each test took to complete
What can you do next?
If a test job fails, you can:
Resolve the problem in your app (if it’s a defect), then rerun the test job
Update the test (if it’s missing a step or needs adjustment), then rerun the test job.
Any new UI tests you create in the future will automatically be included in the next scheduled test job run.