Runs

A run is one execution record. Runs can start from a single test case, a manual plan run, a schedule, or a webhook.

Runs list

Use the Runs list to filter by status and trigger, refresh recent execution state, rerun selected runs, or delete old runs.

Important columns include:

• Run ID.
• Source test case or test plan.
• Trigger.
• Status and result.
• Started, completed, and duration.

Reruns

Rerun after you understand the previous result. Reruns are useful for environment interruptions and validated fixes, but they should not replace failure triage.

Deletion

Delete runs only when the history is no longer useful. Run evidence is often the fastest way to understand whether a failure was a product regression, stale test, or test data issue.