Running Traces

Running Traces Automatically

Once you have created traces by using the Editor, you run them all in parallel by using any of the following methods. Before starting the runs, make sure you’ve setup the test reporting from Settings > Scheduling & Reporting.

1. Running from the Dashboard

Launch parallel trace runs by clicking the ‘Run all Traces’ button on the Dashboard. You can optionally launch a subset of traces by using tags from the button’s dropdown menu, which shows all the tags you have defined.

2. Running by Scheduling

Go to Settings > Scheduling & Reporting and create a schedule. You can set any time interval for how often the traces are run, either for all of them or for trace subsets under certain tags.

3. Running via REST API

Use the API to trigger trace runs with given browsers and tags. You can integrate Usetrace runs to any tool using the REST API.

4. Continuous Integration

For maximal benefit, integrate Usetrace to your team’s continuous integration tool. This means that when your app’s code is updated, your CI tool prepares a build and deploys a new version of your app to a web server automatically. At this point your CI tool calls Usetrace to run all traces against the new version.

Usetrace offers several CI integrations out of the box: Bamboo, CircleCI, Codeship, Jenkins and Visual Studio Online.