All-Purpose Quality Status Report Rikard Edgren
Generic test report:
DateTime ID Author Time for writing report Time maintaining scripts for generating report Application Under Test Areas tested
For each area: Blockers Testers Tester mood Tests planned Tests executed Tests passed Tests failed Tests remaining (untested+fail) Bugs found, per priority Old bugs status (priority, severity, tester, assignee, days active) Bug resolution aggregation
Coverage (overall, or for each area) Requirements coverage Specification coverage Code coverage (statement/decision/condition) Data coverage Models' coverage Model of models coverage Serendipity For each quality characteristic: Importance Measurement scale Points Violations Gut feeling
Enhancements Noteworthy information Other artifacts Obstacles New risks Old risk status Learnings Test plan change requests
Quality assessment Information objectives fulfillment Go/No-go recommendation upcoming activities
This is of course practically useless.
You should report what is important.
I thought you had went a bit mad there, until I read the last two lines.
Very good 🙂