1. Software Testing Principles and Concepts
2. Building the Test Environment
3. Managing the Test Project
4. Test Planning
5. Executing the Test Plan
6. Test Status, Analysis and Reporting
7. User Acceptance Testing
8. Testing Software Developed by Outside Organizations
9. Testing Software Controls and the Adequacy of Security Procedures
10. Testing New Technologies

Back to Certified Manager of Software Testing (CMST)

The testers need to demonstrate the ability to develop testing status reports. These reports should show the status of the testing based on the test plan. Reporting should document what tests have been performed and the status of those tests. To properly report status, the testers should review and conduct statistical analysis on the test results and discovered defects. The lessons learned from the test effort should be used to improve the next iteration of the test process.

Metrics of Testing Metrics specific to testing include data collected on testing, defect tracking, and software performance. Use quantitative measures and metrics to manage the planning, execution, and reporting of software testing, should focus on whether test objectives and goals are being reached.

Test Status Reports
Reports the status of testing as specified in the test plan and would include information on:

1. Test Plan Coverage – percent of test plan completed.
2. Code Coverage – monitoring the execution of software and reporting on the degree of coverage at the statement, branch, or path level.
3. Requirement Coverage – monitoring and reporting on the number of requirements tested, and whether or not they are correctly implemented.
4. Test Status Metrics:
   1. Metrics Unique to Test – includes metrics such as Defect Removal Efficiency, Defect Density, and Mean Time to Last Failure.
   2. Complexity Measurements – quantitative values accumulated by a predetermined method, which measure the complexity of a software product.
   3. Project Metrics – status of project including milestones, budget and schedule variance and project scope changes.
   4. Size Measurements – methods primarily developed for measuring the software size of information systems, such as lines of code, and function points. These can also be used to measure software testing productivity. Sizing is important in normalizing data for comparison to other projects.
   5. Defect Metrics – values associated with numbers or types of defects, usually related to system size, such as “defects/1000 lines of code” or “defects/100 function points”; severity of defects, uncorrected defects, etc.
   6. f. Product Measures – measures of a product’s attributes such as performance, reliability, failure, usability.

Final Test Reports

1. Reporting Tools – use of word processing, database, defect tracking, and graphic tools to prepare test reports.
2. Test Report Standards – defining the components that should be included in a test report.
3. Statistical Analysis – ability to draw statistically valid conclusions from quantitative test results.

Back to Certified Manager of Software Testing (CMST)