# Running Tests and Reading Results

> Run tests on demand or on a schedule, locally or in the cloud, track them in Run History, then read the report to find what caused a failure.

## Guides in this Section

- [Triggering a Run](/docs/running-and-results/triggering-a-run): A run executes one or more Test Cases against one or more Environments. How to start a run, pick your environments and watch the progress live.
- [Scheduling Runs](/docs/running-and-results/schedules): Run tests automatically on a recurring schedule. How to create a schedule, choose tests and environments, set the frequency and manage notifications.
- [The Desktop App](/docs/running-and-results/desktop-app): The Desktop App runs tests on your own machine for Local execution. How to install it, sign in, and when to choose local execution over the cloud.
- [Run History](/docs/running-and-results/run-history): Run History is the complete record of every test run in a project. How to monitor progress, filter by status or environment, and investigate failures.
- [Reading Reports](/docs/running-and-results/reports): A Report holds the full result of one run: status, step results, logs, screenshots and video. How to read it and find the real cause of a failure.