1 Test report Process
2 When test report is created
3 Categories of the Test report (examples)
4 Practices to creating good Test Report
5 Test report shows the status of testing
6 What tests were already performed
7 The status of these tests
8 What is remaining
9 Overall progress
10 Test report should be documented and visible for project team
Test Reporting Process - "When Test Report should be created?"
Pre-defined checkpoints (milestones)
The end of testing stage
Whenever significant problems are detected
Collect Test Status Data
Categories of data:
Test results data
Test case results and test verification results
Defects
Test Result Data
Results pictures: Pass/fail result pictures
Software components, applications for test
Platform – the hardware and software environment in which the software system will operate. Test case & Test verification results
Results describe any variance between the expected and actual outputs
They are results of below test techniques used by the test team to perform testing
Test cases – The type of tests that will be conducted during the execution of tests, which will be based on software requirements
Inspections – A verification of process deliverables against deliverable specifications.
Review checklists – Verification that the process deliverables/phases are meeting the user’s true
needs.
Defects
=> The description of defects:
Name of defect
Status of the defect
Severity of the defect
Type of defect
Module code which contains defect
How the defect was discovered
Data the defect uncovered
Test case of defect
Defect Report
Defect Status Report: see current status of all defect in period of time
Defect Distribution: see defect distribute to QC Activities
Defect Re-Open: see the number defects are re-opened
Defect Summary: see number defect based on Product Type
Defect Trend: see trend of defect
Defect Report - Sample
General Status Report
Defect Distribution
Defect Re-Open
Defect Summary
Defect Trend
Analyze the data
Testers should answer these questions
What information does the project/customer need?
Which metrics are used in Reporting?
Reporting
Testers should answer these questions
How can testers present that information in an easy-tounderstand format?
How can I present the information so that it is believable?
What can I tell the project management/customer that would help in determining what action to take?
Categories of the Test Report (examples)
=> Function test report
=> Test case report:
=> Defect distribution report
=> Defect statement report