Test Management
- In ISTQB, Test Management refers to the planning, organization, control, and monitoring of the testing activities throughout the software development lifecycle. It encompasses all aspects of managing the testing process, including defining test objectives, managing resources, tracking progress, and ensuring that testing is aligned with the project’s overall goals.
Test Planning
- Test planning involves defining the scope, approach, resources, and schedule for the testing activities. It sets the foundation for the entire testing process and aligns it with project objectives.
Key Concepts
-
Test Plan: A document that outlines the test strategy, objectives, resources, schedule, and deliverables for the testing process. The test plan typically covers:
-
Types of Test Plans:
-
Master Test Plan: A high-level plan covering the overall testing for a project.
-
Level Test Plan: A detailed plan for a specific level of testing, such as unit testing, integration testing, or system testing.
-
-
-
Scope: Defines what will be tested (in-scope) and what will not be tested (out-of-scope).
-
Test Objectives: The overall goals of testing, such as identifying defects, verifying functionality, and validating performance.
-
Resources: People, tools, and infrastructure needed for testing.
-
Schedule: The timeline for test execution, including milestones and deadlines.
-
Risks and Contingencies: Identifies risks that could affect testing and how to mitigate them.
Test Control
- Test control involves comparing actual testing progress against the plan and making adjustments as necessary to keep testing on track. It includes measuring the status of testing activities, identifying deviations from the plan, and taking corrective actions.
Key Concepts
-
Test Monitoring: Continuously tracking and measuring the progress of testing activities against the test plan.
-
Test Reporting: Providing stakeholders with regular reports on testing progress, such as test execution status, defect reports, and test coverage metrics.
-
Entry and Exit Criteria: Predefined conditions that must be met before testing can start (entry criteria) or be completed (exit criteria). For example:
-
Entry Criteria: Code completion, availability of test environments, or test data preparation.
-
Exit Criteria: All test cases executed, critical defects resolved, or acceptance criteria met.
-
Test Estimation
- Test estimation is the process of predicting the time, effort, and resources required to perform the testing activities. Accurate estimation is critical for effective planning and resource allocation.
Key Concepts
-
Effort Estimation Techniques:
-
Work Breakdown Structure (WBS): Breaking down testing tasks into smaller, more manageable components and estimating the time for each task.
-
Expert Judgment: Estimation based on the experience of senior testers or managers who have worked on similar projects.
-
Test Point Analysis (TPA): A technique used to estimate testing effort based on the complexity of the system under test and the number of test cases.
-
Wideband Delphi: A consensus-based estimation method where experts discuss and refine their estimates iteratively.
-