Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems, Second Edition

Appendix B. Weekly Status Report Template

• Product Name Status Report

• Report No. 23

• Week Ending Month XX, 200X

• Author

• Month XX, 200X

I. Testing Project Management

1. Project Schedule*

Development Milestone	Date	Testing Milestone[a]	Date
Italicized milestones are completed milestones. [a] [b]
Prealpha	xx/xx/xx	Test plan first draft delivered Test plan second draft delivered Test plan completed/approved	xx/xx/xx xx/xx/xx xx/xx/xx
Alpha	xx/xx/xx	Begin alpha test phase	xx/xx/xx
Beta	xx/xx/xx	Begin beta test phase	xx/xx/xx
Release candidate	xx/xx/xx	Begin final test phase[b]	xx/xx/xx
Golden master	xx/xx/xx	Testing Completed	xx/xx/xx
[a] Also see the detail test schedule in the test plan. [b] Assuming the release candidate is accepted.

2. Progress and Changes Since Last Week

• Completed install/uninstall tests.

• Completed configuration/compatibility tests.

• Regressed all outstanding fixed bugs.

• Completed testing the online help system.

• Reported 16 new bugs.

3. Urgent Items

• LogiGear Testing group still has not received the xxxxx and xxxxx to be included with the product. The missing items might cause a schedule delay of the release candidate.

• It has been three weeks and the majority of memory bugs are still unfixed. This is a very high-risk issue. This might cause a delay in the shipping schedule.

4. Issue Bin

Nonurgent issues to be addressed in the next week or so park here.

5. To-do Tasks by Next Report

• Complete regressing all fixed bugs.

• Deliver final test plan for review and approval.

• Review executed test plans to verify testing completeness. ...