Before you close
Test and Defect Readiness Analyzer
Take the test runs and the defect list into the go/no-go meeting laid against the exit criteria, with the weakest areas and a realistic date for the rest.
Open the test-run export from your test tool and the defect export from your tracker, or either one alone. Both are read inside your browser; nothing is uploaded.
Test runs
Drop a spreadsheet here
An export from the test tool: a test ID, its result (passed, failed, blocked, not run), the area it belongs to and the date it ran. One row per run is fine; the latest counts.
Defects
Drop a spreadsheet here
An export from the defect tracker: ID, severity, status, the date raised and the date resolved, and the area if you have it.
The same questions every go/no-go asks
Has enough of the testing been run? Did enough of it pass? Are there open defects the business cannot go live with? Which areas are behind? And if the answer is not yet, how long until it is? Somebody usually answers these by filtering two exports in a spreadsheet the morning of the meeting. This lays both exports against the criteria in one pass.
Your exit criteria
Set the share of tests that must have run, the pass rate among them, and how many blocked tests and open critical and high defects the meeting will accept. Each is shown as met or not met with the number behind it. The defaults are common ones, not a standard; set your own.
Area by area, and the defects
Areas are ordered weakest first, with passed, failed, blocked and not-run counts and the open defects against each. Open defects are counted by severity and by how long they have been open, the oldest serious ones are listed by name, and a week-by-week view shows whether defects are being closed faster than they arrive.
When the rest would be done
At the pace of the last ten working days, when would the tests not yet run be finished? At the rate critical and high defects have been closing, when would the open ones be inside the criteria? Both are forecasts from the current pace, and the page says what they assume.
What this does not do
It does not make the go/no-go decision. Criteria can be met with a release that should not go, and missed with one that should; that judgment belongs to the people in the meeting. It reads severities and statuses as trackers write them, and lists anything it could not read. It does not know whether a test is a good test.