Functional Testing Status
Functions Working Timeline
Expected verses Actual Defects Detected Timeline
Defects Detected verses Corrected Gap Timeline
Average Age of Detected Defects by Type
Defect Distribution
Relative Defect Distribution
Testing Action
Functional Testing Status
This report will show percentages of the functions which have been:
Fully Tested
Tested with Open Defects
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:
Define Scope of Testing
Present Test Results
Draw Conclusions/Recommendations
Two Goals:
Provide Data for Determination of Readiness by Customer Provide Data for Long Term Detection of Problem Functions.
SOFTWARE QUALITY ASSURANCE AND CONTROLSOFTWARE QUALITY AND COST ASPECT
STABLE PROCESS OF SOFTWARE TESTING
STABLE PROCESS OF SOFTWARE TESTING PART TWO
DEFECTS IN SOFTWARE TESTING
REDUCTION OF DEFECTS IN SOFTWARE TESTING
SOFTWARE TESTING AND EFFECTING FACTORS
SCOPE OF SOFTWARE TESTING
TESTING LIFE CYCLE PART ONE
TESTING LIFE CYCLE PART TWO
TESTING LIFE CYCLE PART THREE
SOFTWARE TESTING AND CONSTRAINTS WITH IN IT
TESTING CONSTRAINTS PART TWO
LIFE CYCLE TESTING
TEST METRICS
Independent Software Testing
Test Process
Testing verification and validation
Functional and structural testing
Static and dynamic testing
V model testing
Eleven steps of V model testing
Structural testing
Execution testing technique
Recovery Testing technique
Operation testing technique
Compliance software testing technique
Security testing technique
No comments:
Post a Comment