5.3. Test Monitoring and Control

Question 1

5.3.1. (K1) Recall metrics used for testing

Answer 1

• Percentage of planned work done in test case preparation (or percentage of planned test cases implemented)
• Percentage of planned work done in test environment preparation
• Test case execution (e.g., number of test cases run/not run, test cases passed/failed, and/or test conditions passed/failed)
• Defect information (e.g., defect density, defects found and fixed, failure rate, and confirmation test results)
• Test coverage of requirements, user stories, acceptance criteria, risks, or code
• Task completion, resource allocation and usage, and effort
• Cost of testing, including the cost compared to the benefit of finding the next defect or the cost compared to the benefit of running the next test

Question 2

5.3.2. (K2) Summarize the purposes, contents, and audiences for test reports____types of reports

Answer 2

The test report prepared during a test activity may be referred to as a test progress report, while a test report prepared at the end of a test activity may be referred to as a test summary report.

Question 3

typical test progress reports may also include:

Answer 3

• The status of the test activities and progress against the test plan
• Factors impeding progress
• Testing planned for the next reporting period
• The quality of the test object

Question 4

Typical test summary reports may include:

Answer 4

• Summary of testing performed
• Information on what occurred during a test period
• Deviations from plan, including deviations in schedule, duration, or effort of test activities
• Status of testing and product quality with respect to the exit criteria or definition of done
• Factors that have blocked or continue to block progress
• Metrics of defects, test cases, test coverage, activity progress, and resource consumption. (e.g., as described in 5.3.1)
• Residual risks (see section 5.5)
• Reusable test work products produced