Software Testing Tutorial
- Introduction to Software Testing
- Principles of Software Testing
- Software Development Life Cycle (SDLC)
- Software Testing Life Cycle (STLC)
- Levels of Testing
- Database Testing
- Ad-hoc Testing
- Testing Types
- Test Closure Report Preparation
- Test Report Preparation
- ISTQB Organization and Certification Overviews
What is the Test Report?
Test Report is needed to reflect testing results in a formal way, which gives an opportunity to estimate testing results quickly. It is a document that records data obtained from an evaluation experiment in an organized manner, describes the environmental or operating conditions, and shows the comparison of test results with test objectives
Test Report is a document which contains a summary of test activities and final test results. An assessment of how well the Testing is performed based on the test report, the stakeholders can Evaluate the quality of the tested product.
Make a decision on the software release. For example, if the test report informs that there’re many defects remaining in the product, the stakeholder can delay the release until all the defects are fixed. Just as effective software testing is important, test reporting is equally valuable in overall QA activities. Test report or test summary report is prepared at the end of every QA cycle. This report highlights facts, risks, accomplishments and important events of the QA cycle.
Test Report Preparation:
Test report typically contains below components:
- Project Name: Name of the project.
- Release Number: This should contain release/build number for which the test summary report is being prepared. Typically it is same as the release number received in current cycle’s release note.
- Tested Items: This section contains items which are tested as part of test execution cycle. List down all the modules which have been released in current build and which are tested in QA cycle.
- Status of Project: Present current status of project. It should contain total number of test cases executed in each browser, passed/failed/pending test cases, total number of defects reported in current test cycle. Also, provide classification of issues as per their priority/severity (Eg. Major, Critical etc.), issue status(Eg. Open, Resolved etc.) and their types(Eg. Bug, Improvement etc.). You can also cover some charts which shows defect distribution, defect detection rate and current state of testing in overall project duration.
- Risks: Provide details about risks which may arise during testing activities in project. This could be too many number of unresolved issues, many Blocker/Critical/Major issues, untested feature, limited testing time etc. Be comprehensive in detailing risks so that preventive measures can be taken at project level by team members.
- Project Health: Highlight overall project health in context of testing. Color coding can be used here to mark overall project health(Red/Orange/Green).
- Conclusion/Remarks: Conclude the report by writing QA decision whether the current build has passed testing.
- All relevant stakeholders of the Project will be able to see the health of AUT (application under test).
- It will help them to take necessary steps proactively, if required.
- It will to justify the testing effort that testing team is putting in the project.
- It will help in building more mature process.
- It should be published after every test run cycle
- It should have relevant metrics like Cost of finding a defect in testing, Test Case Adequacy, Test Case Effectiveness, Test Efficiency, Effort Variance, Schedule Variance, Schedule Slippage, Rework Effort Ratio, Review Effort Ratio, Weighted Defect Density
- Mention all testing activities
- All reports should be maintained in a document repository system
What does a test report contain?
Project Information: All information of the project such as the project name, product name, and version should be described in the test report.
- Project Name
Test Objective: As mentioned in Test Planning tutorial, Test Report should include the objective of each round of testing, such as Unit Test, Performance Test, System Test …Etc.
- Test type
Test Summary: This section includes the summary of testing activity in general.formation detailed here includes
- The number of test cases executed
- The numbers of test cases pass
- The numbers of test cases fail
- Pass percentage
- Fail percentage
Defect: One of the most important information in Test Report is defect. The report should contain following information
- Total number of bugs
- Status of bugs (open, closed, responding)
- Number of bugs open, resolved, closed
- Breakdown by severity and priority
The project team sent you the Defect information as following:
- Defect density is 20 defects/1000 lines of code average
- 90% defects fixed in total
You can represent the data as following graph:
Why Test Reports Are Important?
- It offers knowledge transfers and sharing experience among team members, management, and client to improvement.
- Test reports facilitate to maintain the test record with the required detail. This gives information availability.
- Test report saves the time and effort to put on a project. The information is available to access quickly and effortless.
- This gives the facility to keep the information and will reduce the ambiguity and distraction.
- Versioning provides us the detail on what are the changes done on particular test matter.
- Since we maintain test reports, the other members can review and give the feedback for the betterment of the project.
- It keeps a record of the testing activities carried out. The client will like to see the process and the test carried out.
- We shall analyze the test report and use the lesson learn from it to the future projects.
- It serves as a proof of evidence to the testing carried out.
The points below summarize the topics as discussed:
- Test Report is a document which contains a summary of test activities and final test results.
- Test reports help to make a better decision.
- Test Reportwill to justify the testing effort that testing team is putting in the project.