TM-2.1.3 K4 Analyze
Analyze test results to create test reports that empower stakeholders to make decisions
Test management should understand how to interpret and use metrics to understand and report test status. For higher levels of testing such as system testing, system integration testing, acceptance testing, and security testing, the primary test basis is typically work products such as requirement specifications, use cases, user stories and product risks. Metrics of structural coverage are more applicable to lower levels of testing such as component testing (e.g. statement coverage) and component integration testing (e.g., interface coverage). While test management may use metrics of code coverage to measure the extent to which their tests exercise the structure of the system under test, reporting of higher-level test results should be tailored to the specific context and needs of the project. For example, in frequently changing environments, code coverage metrics may be useful to monitor the impact of code changes on the test suite and identify potential gaps or risks. In addition, test management should understand that even if component tests and component integration tests achieve 100% of their structural coverage, defects and quality risks remain to be addressed at higher test levels.
The objective of reporting metrics is to provide an immediate understanding of the information for management purposes. Metrics can be reported as a snapshot of a metric at a point in time or as the evolution of a metric over time to evaluate trends.
Product risks, defects, test progress, coverage and related cost and test effort are measured and reported in specific ways at the end of the project.
The following are examples of metrics that can be used for different purposes:
Metrics related to product risks include:
These metrics can be used to assess the quality of the test basis and the effectiveness of the test cases in covering the product risks.
Metrics related to defects include:
These metrics can be used to monitor the defect detection and resolution process, identify the areas of high defect density or defect severity, and evaluate the test efficiency and effectiveness.
Metrics related to test progress include:
Metrics related to coverage include:
Metrics related to costs and test effort include:
Additionally, it is useful to combine metrics from different categories (e.g., a metric that shows the correlation between the trends of open defects versus the trends of executed tests, or a metric that shows the quality of the test basis based on the number of defects found in the requirements). When test execution continues and fewer and fewer defects are identified, a decision can be made to terminate the tests. This decision should be based on the reporting of the metrics and the agreed exit criteria.
Termination of contract requires careful consideration of legal, operational, and ethical factors. Proper planning protects organizational interests while maintaining professional standards.
Legal and test policy compliance. Collaboration with people and culture (also known as human resources) supports adherence to employment law, organizational policies, and union agreements where applicable. Documentation requirements vary by jurisdiction and termination type, requiring thorough preparation. Performance improvement plans may be mandatory before termination for cause.
Knowledge transfer and documentation part. The TME identifies critical knowledge held by departing individuals including system configurations, test data locations, and specialized procedures. Next, the TME enables comprehensive handover processes to provide continuity of test activities and secures intellectual property and organizational assets before termination.
Timeline and test communication planning. The TME coordinates termination timing with project schedules to minimize disruption to test activities. The TME plans communication strategies towards team members and stakeholders and considers security implications including system access revocation and confidentiality requirements.
Contractor-specific considerations. The TME reviews contractual obligations including notice periods, deliverable completion requirements, and transition responsibilities. The TME evaluates early termination clauses and associated financial implications.
Termination practices emphasize dignity, transparency, and support for leaving employees while protecting organizational interests.
The learning objectives explained by the sections found for this search, in the same order.
Analyze test results to create test reports that empower stakeholders to make decisions
Explain considerations that must be made when terminating an employee or contractor
None of the sections found for this search explains a learning objective.
No learning objectives match the current filters.
Business outcomes whose code or wording matches your search, with the learning objectives linked to each.
No business outcome matches this search.
No business outcomes match the current filters.
Keywords that the syllabi list at the start of a chapter — ISTQB Glossary keywords and domain-specific keywords — matching your search. Definitions are the ISTQB Glossary's.
No chapter keyword matches this search.
No keywords match the current filters.
Questions from the published sample exams that match your search — in the question, its answer options, or the objective or keyword it tests.
You work for an international company that manufactures hardware and software for telecommunications networks. You are the test manager for a product line of network router software. The hardware development team delivers a new release every six months. The…
You are the test manager of a software project that uses a document-centric sequential development model and involves developing a desktop application for a banking system. The project has a large and hierarchical team that works with multiple stakeholders.…
No sample exam question matches this search.
No exam questions match the current filters.