Template · Test Tracking Workbook
One workbook for everything you track during test execution.Team, environment, coverage, status, metrics.
A multi-sheet workbook that gives a test manager a single pane of glass over an execution cycle. Designed for the volume of data a real program produces, not the volume a demo produces.
- Sheets
- 6+
- Variants
- Basic + Advanced
- Signals
- Team, Env, Coverage, Status
Dashboards without source data are theater. This workbook is the source data, the chart is a byproduct.
Key takeaways
Four things to remember.
01
One book, six sheets
Test Environment, Test Team, Quality Risk Coverage, Test Case Summary, Bug Metrics, Release Readiness. Each sheet feeds the others; none stands alone.
02
Every test case ties to a risk
The Quality Risk Coverage sheet cross-tabulates test cases against the FMEA risks. An uncovered high-RPN risk shows up immediately.
03
Estimate vs. actual, side by side
The Test Case Summary sheet tracks estimated and actual effort for every case. Velocity signals emerge from the difference, not from guesswork.
04
Track the environment explicitly
The Test Environment sheet names every host and its availability status. A "blocked" cycle has a root cause traceable to a named system.
Why this exists
What this template is for.
Most test tracking we inherit is a README, a shared doc, and three Slack channels. This workbook replaces all three with a structured record the whole team edits together.
The Basic variant is four sheets; the Advanced variant adds historical snapshots and a release-readiness view. Pick the one that matches how many releases you run per year, both are useful.
The columns
What each field means.
One row per test host or environment. Track system role, hostname, IP, OS, installed software, and current availability.
Example: DB1 / Kursk / 192.168.6.10 / Solaris / Oracle 9i / Available
Roster of testers, including initials (used elsewhere in the book), full name, title, and working shift.
Example: JHB / Jamal Brown / Test Manager / Split
Matrix cross-tabulating test suites / cases against the FMEA risks. Cell values indicate coverage strength (e.g., 9 = full, 3 = partial, 1 = incidental, 0 = none).
Example: Test 1.001 (File) covers risk 1.001 with weight 9 (full coverage).
Row per test case. Tracks developer, executor, Test ID, name, status, type (Auto / Manual), phase, estimated effort, actual effort, estimated duration, and comments.
Example: ATE / TT / 1.001 / File / Update / Auto / IS / 2 est / 6 act / 4 duration
Running counts of bugs by severity × priority, opens vs. closes per cycle, fix velocity, and regression rate. Feeds the dashboard charts.
Example: Severity 1 × Priority 1 = 3 open; 2 closed this cycle; regression rate 4%.
Summary view rolling up coverage, status, and bug metrics into release-go/no-go signals for leadership.
Example: Coverage: 78% of high-risk; Status: 62% passed; Bugs: 2 sev-1 open.
Live preview
What it looks like populated.
Test Environment sheet from the Basic Sumatra Test Tracking workbook.
| System | Name | IP Address | OS | Other SW | Status |
|---|---|---|---|---|---|
| Server Cluster East (SE) | |||||
| DB1 | Kursk | 192.168.6.10 | Solaris | Oracle 9i | Available |
| Web1 | Leningrad | 192.168.6.20 | Solaris | Netscape | Available |
| App1 | Stalingrad | 192.168.6.30 | HP/UX | Oracle 9AS | Available |
| Server Cluster West (SW) | |||||
| DB2 | Dunkirk | 192.168.6.11 | AIX | Sybase | Available |
| Web2 | Bulge | 192.168.6.21 | AIX | Domino | Available |
How to use it
7 steps, in order.
- 1
Populate the Test Team sheet with every person who will log test results. Use initials consistently in downstream sheets.
- 2
Populate the Test Environment sheet with every host the test lab will use. Mark availability before each cycle.
- 3
Import your FMEA into the Quality Risk Coverage sheet as column headers. Create one row per test suite / case.
- 4
Fill coverage values (9 / 3 / 1 / 0) for each test case against each risk. Sort by risk RPN to spot uncovered high-risk cells.
- 5
In Test Case Summary, enter estimated effort and duration for every case before execution starts. Fill in actual effort as execution progresses.
- 6
Update Bug Metrics daily during execution. Use the shift transition as the natural checkpoint.
- 7
At each release gate, review the Release Readiness roll-up with stakeholders. If it cannot answer their questions, iterate the underlying sheets.
Methodology
The thinking behind it.
The Basic variant is enough for teams running 3–6 test cycles per release. The Advanced variant adds historical snapshot sheets and a read-only dashboard tab suitable for programs running 20+ cycles per year.
The coverage weights (9 / 3 / 1 / 0) come from QFD (Quality Function Deployment). They force a step-function judgment instead of arbitrary percentages.
Take it with you
Download the piece you just read.
The library is free. Tell us who you are so we can send you updated versions. One form; this browser remembers you after that.
In the library
Pair this with.
Process · Test Execution
Run the tests, capture the data, adjust daily.
Test execution is where the risk register becomes results. These eight steps cover selection, assignment, the per-test inner loop, blocking-issue resolution, and the daily replanning that keeps a cycle on the rails.
Read →Process · Test Results Reporting
Report test results as answers, not data.
Test reports fail when they present numbers nobody asked for. This five-step process starts with the audience, derives the questions, picks the metrics, and tunes the report until it is actually used.
Read →Template · FMEA Quality Risk Analysis
A working FMEA for software, not a form.
The Sumatra FMEA is a Failure Mode and Effects Analysis adapted from aerospace and automotive practice for software quality risk. It converts stakeholder judgment into a defensible, numerically prioritized register you can defend to any audience.
Read →Process · The Master Framework
Four phases, applied in order, every project.
The top-level testing process used on every engagement. Four phases contain twelve sub-processes, each of which is documented in its own checklist in this library.
Read →
Keep reading
Related reading
- Primer
Careers in Software Quality: Roles, Skills, and First Steps
What testers, test automation engineers, quality engineers, and test managers actually do, the skills each role uses, and practical first steps for students and career changers, including the ISTQB Foundation certification.
Read → - Primer
Errors, Defects, and Failures: What a Bug Really Is
Everyone says 'bug', but testers use three precise words: error, defect, and failure. Learn the difference, why it matters, and how severity and priority decide which problems get fixed first.
Read → - Primer
How Software Gets Attacked: Common Vulnerabilities in Plain English
The most common ways attackers break into software, explained without jargon: trusting input, broken access control, weak sign-in, misconfiguration, and outdated components. Each one comes with the defense that stops it.
Read → - Primer
How to Report a Bug So It Actually Gets Fixed
Finding a bug is half the job. Learn how to write a bug report a developer can act on: a clear summary, exact steps to reproduce, expected versus actual results, and the habits professional testers use to make every report count.
Read → - Primer
Security Testing Basics: Finding Weaknesses Before Attackers Do
An introduction to security testing for new testers and developers: thinking in threats, designing abuse cases, testing access control, the role of automated scanners and penetration tests, and the rules that keep security testing legal and ethical.
Read → - Primer
Staying Safe Online: Passwords, Sign-In, Phishing, and Updates
The everyday security habits that stop most attacks: strong unique passwords, multi-factor sign-in, spotting phishing, keeping devices updated, and sharing carefully. Written for students, families, and anyone starting out.
Read →
Practices
Where this leads
- QA & testingSoftware testing
Software quality consulting since 1994: we test the releases that matter, coach your team on the method, and measure how its testing matures.
Book a call →