Browse QA Engineers Section 9: Test Reports & Metrics

Test Execution Report

11 fill-in slots · from The AI Prompt Handbook for QA Engineers

Your details

0/11 filled

Test Execution Report

Generate a test execution report from these results.

TEST RUN:
- Date: [Date]
- Sprint: [Sprint number]
- Feature: [What was tested]
- Platforms tested: iOS [version, device] and Android [version, device]

RESULTS:
- Total test cases: [Number]
- Passed: [Number]
- Failed: [Number]
- Blocked: [Number]
- Not executed: [Number]

FAILED TESTS:
1. [Test name]: [Failure reason, bug ticket if filed]
2. [Test name]: [Failure reason]
3. [Test name]: [Failure reason]

BUGS FOUND THIS CYCLE:
1. [Bug title]: [Severity, Status]
2. [Bug title]: [Severity, Status]

Generate a report with:
1. Executive summary (2-3 sentences for stakeholders)
2. Pass rate and trend (compared to previous sprint if available)
3. Risk assessment (are the failures concerning? any patterns?)
4. Blocked items and what's needed to unblock
5. Coverage gaps (what wasn't tested and why)
6. Recommendation: [Ready for release / Needs more testing / Not ready]

Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.