About this tool
At the end of a test cycle, stakeholders want three answers: how much was tested, how much passed and whether it is safe to release. This report computes pass rate as passed ÷ (passed + failed), so blocked and skipped tests do not inflate or deflate it, and execution progress as everything attempted ÷ total, so untested work stays visible. It warns when the status counts do not add up to the total and when a Go recommendation sits next to failed tests or Critical defects. The HTML output uses table layout and inline styles because most email clients ignore stylesheets, and "Copy for email" puts formatted HTML on the clipboard for pasting into Outlook or Gmail.
How to use it
- Enter the build, test dates and environment.
- Fill in the counts for total, passed, failed, blocked, skipped and not run, and the defects raised by severity.
- List the key issues and choose Go, Go with risks or No-go.
- Copy the Markdown or plain text, or use the HTML email format and "Copy for email".
Test Execution Report FAQ
Why is pass rate calculated on executed tests only?
Blocked and skipped tests never ran, so they could neither pass nor fail. Including them in the denominator hides real failures behind untested work. Execution progress is reported separately so the untested part stays visible.
What does "Go with risks" mean?
The release can proceed, but known issues or untested areas remain and have been accepted by the decision makers. List them under Key issues so the risk is explicit and recorded.
Why do the numbers not add up?
Total should equal passed + failed + blocked + skipped + not run. If it does not, a test was double-counted or missed. The tool shows the difference so you can fix it before sending the report.