Test run
Also called: Test cycle, Test execution (Xray)
One execution of a chosen set of test cases on a specific build and environment, with a result for each case.
Definition
A run is created from cases in the repository, tied to one build and one environment or device, and assigned to testers. As they work, each case gets an execution status. The run is the record of what was actually tested, where, by whom and with what outcome. Tools name it differently: test run, test cycle or test execution.
In practice
"FoodDash 2.0.0 regression, build 412, iPhone 15 (iOS 18)": 120 cases, 104 passed, 9 failed, 3 blocked, 4 untested.
Learn it in context
Lessons that use this term.
Related terms
- Test executionThe activity of running test cases, comparing actual with expected results and recording the outcome.
- Execution statusThe result recorded for a test case in a run: Passed, Failed, Blocked, Retest, Skipped or Untested.
- Test case repositoryThe central library where a team keeps all its test cases, organized into sections and suites.
- Test summary reportA report at the end of testing that summarizes what was tested, results, open bugs, risks and a recommendation.