Understand Results
Open a run from your project’s Results tab to see what the agent did, what it observed, and why the test passed or failed.
Execution status and test outcome
TesterArmy separates whether execution finished from whether the tested behavior worked.
Do not treat completed by itself as a passing result. Always check the test outcome.
Step results
Each step shows its progress, summary, and any failure information. Start with the first failed step: later failures are often consequences of the same blocker.
When a result is unclear, compare the written step with Write Reliable Test Steps. Focused steps with one intent produce more useful evidence.
Issues and screenshots
Reported issues explain product behavior that prevented a step from passing. Screenshots provide visual evidence from important points in the run and make it easier to distinguish an application regression from an incorrect target or test instruction.
Video
Completed web and mobile runs include a recording when video capture is available. Use it to understand navigation, transient UI, or the state immediately before a failure. See Run Videos.
Share a result
Use the run actions to enable sharing and copy a read-only link. Disable sharing when the recipient no longer needs access. Review screenshots, URLs, and test data before sharing a run outside your team.
What to do after a failure
- Confirm the run used the expected environment and target URL.
- Review the first failed step, its screenshot, and issue summary.
- Check whether login or site protection blocked access.
- Retry once if the failure appears transient.
- Split or clarify broad test steps before retrying again.
See Run Troubleshooting when execution failed before producing a normal test outcome.