Why Shouldn’t Weekly Status Reports Be Ignored?

Those, who are involved in web site testing, desktop testing and mobile application testing, know that these activities assume writing many different reports besides error reports.

Weekly status reports are required at most of the projects. They are created by the test team every week and are considered to be a part of routine work during functional testing, security testing, load testing and so on. 

A Weekly Status Report Usually Comprises Such Data:

  • the author of the report;
  • the date;
  • the project name;
  • defects that testers consider to be serious; testers don’t allow the project to move forward before fixing the defects;
  • defects that can be corrected later but the managers should know about them;
  • the project progress for the week, closed and pending defects;
  • written, passed, failed and pending test cases;
  • scope of work and priorities for the next week.

Weekly reports may be more or less detailed. Testers may mark different points with different colors to make the reports more readable and underline the most important issues.

Some managers do not require preparing weekly reports, but specialists in manual and automated testing recommend writing them as they can be used for assessing the testers’ work and tracking the project progress.