:

1. Functional Testing Status

2. Functions Working Timeline

3. Expected verses Actual Defects Detected Timeline

4. Defects Detected verses Corrected Gap Timeline

5. Average Age of Detected Defects by Type

6. Defect Distribution

7. Relative Defect Distribution

8. Testing Action

Functional Testing Status

This report will show percentages of the functions which have been:

1. Fully Tested

2. Tested with Open Defects

3. Not Tested

Functions Working Timeline

This Report will show the actual plan to have all functions working verses the current status of functions working.

An ideal format could be a line graph.

Expected verses Actual Defects Detected

This report will provide an analysis between the number of defects being generated against the expected number of defects expected from the planning stage.

Defects Detected 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.

Average Age Detected by Type. This report will show the average days of outstanding defects by step (Sev 1, Sev 2, etc..). In the planning stage, it is beneficial to determine the acceptable open days by defect type.

Defect Distribution

This report will show the defect distribution by function or module. It can also items such as numbers of tests completed.

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 Actions

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.

Final Test Report

Objectives:

1. Define Scope of Testing

2. Present Test Results

3. Draw Conclusions/Recommendations

Two Goals:

Provide Data for Determination of Readiness by Customer Provide Data for Long Term Detection of Problem Functions.

RELATED POST

TEST METRICS

Related Posts

Compliance Testing technique Recovery testing technique Execution testing Structural software testing Static and dynamic testing Functional and structural testing Testing verification and validation Test Process Independent Software Testing and part two Testing metrics and Life cycle testing c programming break statement V model Software Testing Security Testing Technique

Other Programming Courses :

ASP.NET part one and two
Programming with C and C Sharp
Dot Net Complete Course Part one and two
Interview Questions in dot net and asp.net part one part two
Software Testing Complete course part one and two
Interview Questions in software Testing
Complete software testing course here as basic and advanced parts .

Thank you for visiting PROGRAMMING BLOG. If you liked the post, please subscribe to my blog via email or RSS FEED.You can contact me here for any specific feed back .