We will start again with why, so why test reports are important. So every activity should finish with a report in many industries. That will track information about the activities from all stages of testing. This blog will not be only about reported, here I would like to introduce you with theoretical idea of Software testing life cycle, and how to create a great test report in final stage: Test Cycle Closure
Stages of Testing
There are different stages in Software Testing Life Cycle:
Requirement Analysis
Test Planning
Test Case Development
Environment Setup
Test Execution
Test Cycle Closure
So this is an ideal theoretical way, we in Testera are striving to this method, and depending on client requirements we are adopting, but trying to have all these cycles. Ideally,the new stage should be started only if exit criteria from the previous stage are met. Let's suppose that we all know what is expected in every STLC stage, and go fast forward to Test Cycle Closure.
Test Closure Report
So how to start a test closure report? Let's suppose that we meet all exit criteria and had a successful test execution. So the test closure report has to cover various details about the process of testing. Quantitative data should be involved as results of test execution, a number of found defect, defect trend analysis, etc. Because Test Closure Report will be read by many stakeholders of the project, it needs to be simple and accurate. Purpose of every report is to give precise information for decisions.
After reading Test Closure Report, decisions maker should get clear info about project description, test scope, test results, quality of software like test coverage and results, defect metrics, by type and status, outstanding issues and exit criteria. Finally what is learned should be written, like analysis and resolution, lesson learned, best practices adopted and new improvements implemented
Σχόλια