Test Status Reporting - A Software Test Engineers Responsibility

Testing is carried out primarily for unearthing all defects in the system and to prevent a defective product reaching the customers. Secondly, Testing is also carried out to convince the customer that the product conforms to and fulfills the specifications and provides the functionalities that were agreed.

These objectives of testing can be achieved only through proper test planning, test preparation, test execution and test reporting. Test Reporting unlike test planning, preparation and execution plays a vital role in the Software Test Phase.

Many a times
Software Test Engineers fail to understand the real importance of test status reporting and assume that test reporting is Test Lead/ Manager’s responsibility.

The fact is that Test reporting is the fundamental responsibility of the test engineer’s job profiles which most of the
Software Test Engineers underestimate its significance and fail to perform.

Software Test Engineers often report on the execution status in the following ways i.e., in Status Meetings, Verbally communicated F2F or phone to the Lead/Manager, Pass/fail status in the mail, etc…

A good test report not only provides on the completeness of testing but also on the release worthiness to the next level.

The following are the advantages of good Test Summary Report:

  1. Provides summary snapshot on the test status to the Management
  2. Completeness of Testing
  3. Testers taking ownership in decision making
  4. Superiors gain confidence in the tester recommendations.
  5. Record of open issues/risks
  6. Release worthiness/Confidence of the build
  7. Documented and tracked.

A sample test summary report submitted by Software Test Engineer at the end of test execution cycle shall contain the following details:

Prashant Vadher - Test Status Reporting after Software Testing - A Test Engineers Responsibility

Thanks & Regards,

Prashant Vadher | QA Engineer


halperinko said...

1. An issue often neglected, is the ability to run debriefing on a set of test results, and "regroup" accordingly.
While in SBTM debriefing is quite common, other types of testing often do not set the time for that, and loose valuable insights.

2. These days with all the free ALM tools, one can easily track all these details with much less dedicated effort.

@halperinko - Kobi Halperin


Thanks for announcement this advisory article.
university help

Post a Comment

Design by Prashant Vadher