Test Status Report: [Project or release name], [reporting period]
Periodic test status report that tells stakeholders, during testing,
where testing stands against the test plan: progress, what is blocking
it, the measures behind the judgement, new and changed risks, and what
happens next. The structure follows the test status report information
item of ISO/IEC/IEEE 29119-3:2021 (clause 7.3). Issue it on a fixed
cadence (weekly or per sprint) from the start of test execution until
the test completion report replaces it. Replace every [bracketed]
value and every row marked Example.
Document control
| Field | Value |
|---|
| Document ID | [TSR-PROJECT-nn] |
| Project / release | [Quillfern Desk 5.3] (Example) |
| Test plan reported against | [TP-QD53-001 version 1.2] (Example) |
| Test level or scope | [System test / Whole project / Performance] |
| Reporting period | YYYY-MM-DD to YYYY-MM-DD |
| Report number | [3 of a planned 5] (Example) |
| Version | [1.0] |
| Status | [Draft / Issued] |
| Owner | [@test-manager] |
| Distribution | [Product owner, engineering lead, release manager, support lead] |
| Classification | [Internal] |
| Last updated | YYYY-MM-DD |
Revision history
| Version | Date | Author | Change summary |
|---|
| 1.0 | YYYY-MM-DD | [@name] | Issued |
| [1.1] | YYYY-MM-DD | [@name] | [Correction, for example a measure restated] |
1. Test status summary
| Item | Value |
|---|
| Overall status | [On track / At risk / Off track] |
| Reason | Example: At risk: execution is 7 test cases behind plan and 5 cases are blocked (PDF export environment, ticket board rework, expired sign-on accounts) |
| Forecast to meet exit criteria | Example: YYYY-MM-DD, two working days after the planned date, if the environment is restored by YYYY-MM-DD |
| Decisions needed | Example: Approve one extra tester for week 4 (DEC-01) |
Status scale: On track, the plan and exit criteria will be met with
current resources; At risk, they will be met only if a named action
succeeds; Off track, they will not be met without a change of scope,
date or resources.
2. Reporting period
| Item | Value |
|---|
| Period | YYYY-MM-DD to YYYY-MM-DD (week [3] of [5]) |
| Builds tested | [5.3.0-rc2 (to YYYY-MM-DD), 5.3.0-rc3 (from YYYY-MM-DD)] (Example) |
| Environments used | [System test environment ST-2; PDF export service in ST-2] |
| Previous report | [TSR-QD53-02] (Example) |
3. Progress against the test plan
3.1 Execution progress (cumulative)
| Week | Planned executed | Actual executed | Actual as % of plan |
|---|
| W1 (Example) | 50 | 46 | 92.0% |
| W2 (Example) | 110 | 98 | 89.1% |
| W3 (Example) | 170 | 163 | 95.9% |
| W4 | 220 | [n] | [%] |
| W5 | 240 | [n] | [%] |
3.2 Execution by feature area (end of period)
| Feature area | Planned | Executed | Passed | Failed | Blocked | Not run |
|---|
| Ticket board (Example) | 60 | 38 | 35 | 3 | 2 | 20 |
| Assignee picker (Example) | 40 | 30 | 28 | 2 | 2 | 8 |
| PDF export (Example) | 50 | 35 | 32 | 3 | 1 | 14 |
| Customer portal (Example) | 90 | 60 | 56 | 4 | 0 | 30 |
| Total | 240 | 163 | 151 | 12 | 5 | 72 |
Example interpretation: 163 of 240 planned test cases (67.9%) have
been executed against 170 planned by now; the pass rate of executed
tests is 92.6% (151 of 163). The ticket board is furthest behind (38
of 60, 63.3%), and two of its cases wait for the drag-and-drop rework
for accessibility issue ACR-ISS-001 (BLK-02).
3.3 Other planned activities
| Activity | Planned by end of period | Actual | Variance and reason |
|---|
| Regression automation (Example) | 30 new automated checks | 26 | Four checks wait for stable assignee picker IDs |
| Accessibility retest (Example) | Retest ACR-ISS-002 and ACR-ISS-007 | Done | None |
| [Activity] | [Planned] | [Actual] | [Variance] |
4. Factors blocking progress
| ID | Blocker | Tests blocked | Owner | Needed by | Status |
|---|
| BLK-01 (Example) | PDF export service in ST-2 returns timeouts for files over 5 MB | 1 | [@platform-lead] | YYYY-MM-DD | Open, fix deployed to ST-3 only |
| BLK-02 (Example) | Ticket board drag-and-drop rework not merged | 2 | [@frontend-lead] | YYYY-MM-DD | In review |
| BLK-03 (Example) | Test accounts for the single sign-on provider expired | 2 | [@identity-admin] | YYYY-MM-DD | Renewal requested |
| [BLK-nn] | [Blocker] | [n] | [@owner] | YYYY-MM-DD | [Status] |
The blocked counts add up to the 5 blocked test cases in table 3.2.
5. Test measures
5.1 Defects
| Measure | This period | Cumulative |
|---|
| Defects opened (Example) | 11 | 34 |
| Defects closed (verified fixed, rejected or duplicate) (Example) | 9 | 21 |
| Defects open at end of period (Example) | | 13 |
| Severity | Open at end of period |
|---|
| S1 Critical (Example) | 0 |
| S2 Major (Example) | 3 |
| S3 Minor (Example) | 7 |
| S4 Cosmetic (Example) | 3 |
| Total | 13 |
5.2 Other measures
| Measure | Definition | Value | Target or threshold | Trend |
|---|
| Pass rate (Example) | Passed / executed | 92.6% | >= 95% at exit | Up from 90.8% |
| Requirements with at least one passed test (Example) | Covered must-have requirements / all must-have requirements | 71 of 98 | 98 of 98 at exit | Up |
| Automated regression suite duration (Example) | Wall-clock time on CI | 31 min | <= 45 min | Stable |
| Average retest turnaround (Example) | Days from fix to retest verdict | 1.4 days | <= 2 days | Stable |
| [Measure] | [Definition] | [Value] | [Target] | [Trend] |
6. New and changed risks
| ID | Risk | Change | Likelihood / impact | Response | Owner |
|---|
| R-07 (Example) | PDF export timeouts hide defects in large exports | New | Medium / High | Run large-file cases in ST-3 while ST-2 is fixed | [@test-lead] |
| R-03 (Example) | Late merge of ticket board rework leaves too little regression time | Raised from Low to Medium likelihood | Medium / Medium | Extra tester in week 4 if DEC-01 approved | [@test-manager] |
| [R-nn] | [Risk] | [New / Raised / Lowered / Closed] | [L / I] | [Response] | [@owner] |
Full register: [link to the project risk register].
7. Planned testing for the next period
| Planned activity | Build | Dependencies | Owner |
|---|
| Execute remaining ticket board and assignee picker cases (28) (Example) | 5.3.0-rc3 | BLK-02 resolved | [@tester] |
| Large-file PDF export cases (Example) | 5.3.0-rc3 | BLK-01 resolved or ST-3 booked | [@tester] |
| Portal regression, second half (30 cases) (Example) | 5.3.0-rc3 | None | [@tester] |
| [Activity] | [Build] | [Dependency] | [@owner] |
8. Decisions and actions
| ID | Decision or action | Requested from | Due | Outcome |
|---|
| DEC-01 (Example) | Approve one extra tester for week 4 | [@product-owner] | YYYY-MM-DD | [Pending] |
| ACT-04 (Example) | Renew single sign-on test accounts (BLK-03) | [@identity-admin] | YYYY-MM-DD | [Pending] |
| [ID] | [Decision or action] | [@name] | YYYY-MM-DD | [Outcome] |
9. References
- Test plan: [TP-QD53-001] (see
quality/test-plan-29119)
- Previous status report: [TSR-QD53-02]
- Test management and defect tracker queries: [links]
- At the end of testing this series is replaced by the Test Completion Report (
quality/test-completion-report)
- Incidents raised in this period: Test Incident Report (
quality/test-incident-report)
- ISO/IEC/IEEE 29119-3:2021, Software and systems engineering: Software testing: Part 3: Test documentation, second edition (2021-10). Official text: ISO, IEC and IEEE, purchase or licensed access: https://www.iso.org/standard/79429.html and https://standards.ieee.org/ieee/29119-3/7499/
Standard and licence note
Structure aligned with ISO/IEC/IEEE 29119-3:2021, Software and systems
engineering: Software testing: Part 3: Test documentation, test status
report information item (clause 7.3: test status, reporting period,
progress against the plan, factors blocking progress, test measures, new
and changed risks, planned testing). The standard is copyrighted and is
cited by name, edition and clause number only; no text, table or
example from it is reproduced, and all wording here is original. Check
the current edition before claiming conformance. Official text: ISO,
IEC and IEEE, purchase or licensed access, at the links in section 9.
Template licence: MIT.