Skip to main content

Running your first Test job with Automated Testing

A step by step guide to schedule your first test job for an automated regression suite

Gino Toro avatar
Written by Gino Toro
Updated yesterday

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.

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 Job, 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

  1. In Gearset, open UI Testing from the main menu.

  2. Click New test job.

Fill in the job details

In the Job details step:

  1. Enter a name, for example Full Regression.

    Note: All UI tests will be included in this Test Job.

  2. Select the Salesforce Organisation you want to run your tests on.

  3. You can also choose how often the job should run automatically:

    1. Daily → select a time.

    2. Weekly → select a day and time.

  4. 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 the Full Regression 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 the Full Regression Test Job again to reopen the side panel.

From here, you can review:

  • The Salesforce organisation 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.

Did this answer your question?