What is reporting in software testing and why its needed? What are different types of reports that can be generated as a part of a test execution phase.
2. Agenda
Test reporting in STLC
Advantages of reporting
When to create reports?
What are different types of reports?
3. Test Reporting in STLC
Software test life cycle consists of different components such as
Understanding the requirement
Creating test plan
Creating and/or re-using the existing test cases
Creating test cycle to plan the test execution
Create and retest identified defects
Each phase has a certain time limit hence its required to plan each task as per the
schedule
Test reporting is the part of test execution phase
4. Test Reporting
Reports are crucial part of software test life cycle
Reports are evidences that are produced during and/or after the test execution
phase
This is the important artifact which can be shared with the project stakeholders to
update about the current progress of the project
It is helpful to know if team has any obstacles or any blockers and it can be
addresses early in the phase
Reports helps to know the percentage of the passed, failed, blocked and yet to
run test cases
5. When to create report?
Software tester, test analyst or test managers can produce the reports during the
test execution phase
It can be created either at mid or end of the cycle or once the test execution phase
is over
Test execution reports generated at the end of each test execution cycle helps to
know the progress of the selected cycle
Test execution report generate at the end of test execution phase gives us idea
about the blocked or known issues identified by the team and blocked test cases
with the their priorities
It helps managers or leads to take the go or no go decisions for the product
release
6. Types of test reports
There are various types of reports that testers can generate using the test
management tools. Some of them are listed below:
Test Plan execution status report
Test cycle execution report
Requirement coverage report
Test case execution report
Defect matrix report
Test case burndown report