Running your first test

How to actually initiate and trigger runs of your tests.

🚧

Before you continue...

To run your test, you first have to have built a test in Waldo. Make sure to read Creating your first test prior to attempting anything in this article.

Skip To:

  • Manual test runs
  • Automated test runs
  • Test runs with CI
  • Validated
  • Scheduled

Manual test runs

📘

For first time users:

Manually triggering your test run is recommended for your first use of Waldo.

  1. Click the Runs icon (stoplight) in your lefthand, sidebar menu
  2. In the upper righthand corner, click Run Tests
  3. You will now be prompted to customize the run
    a. Select the build you want to run the tests on
    b. Select the device you would like to use for your test
    c. Select the test or tests you would like executed using that build
  4. Click “Run all —- tests” in the bottom right corner of the module

Automated test runs

When auto test is enabled in Waldo, all enabled tests will run every time a new build is uploaded.


Test runs with CI integration

❗️

Remember:

For this type of run to be successful, you have to correctly integrate your CI with Waldo and ensure that it is stable.

Lastly, you can trigger a run of one or more test flows for your app with Waldo CLI. This is convenient when you want to trigger a run via CI. Simply add the following to your CI script:

$ waldo trigger --upload_token 0123456789abcdef0123456789abcdef

🚧

Important Note

Make sure you replace the fake upload token value shown above with the real value for your Waldo app.

You can also use an environment variable to provide the upload token to Waldo CLI:

$ export WALDO_UPLOAD_TOKEN=0123456789abcdef0123456789abcdef$ waldo trigger

A run of this kind is tagged as ci-trigger.

📘

A note on CI integration with Waldo

Once your CI is setup, Waldo automatically uploads a build on your next commit. It's important to ensure that your CI is configured to upload simulator builds. If the wrong app file is uploaded, your upload will be marked as failed in your Builds list.

20002000

Did this page help you?