# Review Execution Output

# Review Execution Output

Execution Output provides run-level details, errors, and evidence collected during a test. Use it to understand whether a failure came from the scenario, test data, environment, or application under test.

## What to review

- Error messages and stack traces tied to failed steps or requests.
- Screenshots, logs, or response details captured during execution.
- Timing patterns that point to slow pages, services, or environment issues.
- Test data consumed by the failed flow when available.

## Good practices

1. Start with the first meaningful failure, not every downstream symptom.
2. Compare output with a known good execution when possible.
3. Attach relevant output details to the defect or maintenance ticket.

**Last updated:** September 18, 2026