31-10-2012, 01:10 PM
Test Reporting
Test Reporting.ppt (Size: 137.5 KB / Downloads: 34)
Interesting Points
Effective reporting cannot be accomplished unless a complete test plan is ready by QA.
Development is about breaking down of high level requirements to lower levels, while QA goes in the opposite direction.
Functional Matrix
The purpose of creating a functional matrix
is to show the test plan and order of testing to perform complete testing.
This can also be used to show the progress of testing as complete.
Eight Interim Reports:
Functional Testing Status
Functions Working Timeline
Expected verses Actual Defects Uncovered Timeline
Defects Uncovered verses Corrected Gap Timeline
Average Age of Uncorrected Defects by Type
Defect Distribution
Relative Defect Distribution
Testing Action
Defects Uncovered verses Corrected Gap
This report, ideally in a line graph format, will show the number of defects uncovered verses the number of defects being corrected and accepted by the testing group.
If the gap grows too large, the project may not be ready when originally planned.
Relative Defect Distribution
This report will take the previous report (Defect Distribution) and normalize the level of defects.
An example would be one application might be more in depth than another, and would probably have a higher level of defects.
However, when normalized over the number of functions or lines of code, would show a more accurate level of defects.
Testing Action
This report can show many different things, including possible shortfalls in testing.
Examples of data to show might be number of Sev 1 defects, tests that are behind schedule, and other information that would present an accurate testing picture.