ISTQB Chapter 5 - Test Management - Learning Objectives (9 points)
Identify factors that influence the effort related to testing
Risks, size of product, development model, test approach, time pressure, skills/exp of team, leadership, number of defects, rework required.
Differentiate between various test strategies
Analytical - risk-based testing is an example. Model-Based - state models and reliability growth models. Methodical - systematic use of predefined set of test conditions. Process-compliant - testing based on external rules/standards. Directed - tests driven by experts, SME. Regression-averse - tests to avoid regression of existing capabilities. Reactive - exploratory testing is an example.
Write a defect report, covering defects found during testing
Defect reports include: identifier, title, short summary, date, author, environment, SDLC phase when found, description of defect, logs, screenshots, expected and actual results, severity, and priority to fix.
Give examples of potential entry and exit criteria
Entry Criteria - test reqs, user stories, availability of test environment, test tools, test data. Exit Criteria - planned tests have been executed, coverage achieved, unresolved defects limited, remaining defects low, quality met.
Explain the benefits and drawbacks of independent testing
Independent testers are likely to recognize different kinds of failures compared to developers because of their different backgrounds, technical perspectives, and biases. Isolation from the development team, leading to a lack of collaboration, delays in providing feedback to the development team, or an adversarial relationship with the development team.
Summarize how configuration management supports testing
It tracks all test items and keeps traceability throughout test process.
Explain the difference between two estimation techniques: the metrics-based technique and the expert-based technique
Metrics-based technique: estimating the test effort based on metrics of former similar projects, or based on typical values. Expert-based technique: estimating the test effort based on the experience of the owners of the testing tasks or by experts.
Summarize the purpose and content of a test plan
Outlines test activities including: determining scope and risks, define approach, staffing, scheduling, monitoring, budgeting etc.
Recall metrics used for testing
Percentage of planed work. Test case execution. Defect info. Test coverage of reqs, risks, or code. Task completion. Cost of testing.
Distinguish between project and product risks
Product risk involves the possibility that a work product (e.g., a specification, component, system, or test) may fail to satisfy the legitimate needs of its users and/or stakeholders. Project risk involves situations that, should they occur, may have a negative effect on a project's ability to achieve its objectives.
Summarize the purposes, contents, and audiences for test reports
Summarize/communicate test activity audience. Includes: tests performed, plan deviations, exit criteria, metrics of defects, coverage, etc., future risks, reusable test products.
Identify the tasks of a test manager and tester
Test Manager - Develop/review test strategy, plan test activities, develop skills/careers of testers. Tester - review test plans, prepare test data, execute tests, review tests.
Describe, by using examples, how product risk analysis may influence the thoroughness and scope of testing
The analysis determines test techniques, types of testing, extent of testing, and prioritizes testing.
Define risk level by using likelihood and impact
The level of risk is determined by the likelihood of the event and the impact (the harm) from that event
Apply knowledge of prioritization, and technical and logical dependencies, to schedule test execution for a given set of test cases
The test execution schedule should take into account such factors as prioritization, dependencies, confirmation tests, regression tests, and the most efficient sequence for executing the tests.
