ISTQB Section 5 (Test Management)

   (back to Introduction article with links to all parts) 

---------- Section 5 ------------

Test Management

Product risks (unreliable architecture, code not performing intended functions, performance issues, user experience feedback)  

VS 

Project risks (delays, inaccurate estimates, late changes)


Level of risk = Probability of the risk * Impact if it did happen


Levels of Independent Testing (from most dependence to more independence): Developer, team tester, independent team tester, customer, outsourced team tester;


Tasks of the Test Manager: test strategy, plan test activities, share the perspective, coordinate, test reports, advocate testers, tools, metrics, design test environment, develop tester's skills;

Tasks of the Tester: contribute to the test plan, analyze for testability, create tet conditions, implement test environment, implement tests, prepare test data, execute and log the tests, use tools, automate tests;


Test Strategies:

analytical - testing based on analysis of some factor, risk-based strategy, requirements-based strategy

model-based - design or benchmark of some model our system must follow, the model will be based on some required aspect of the product

methodical - failure-based, checklist-based, quality-characteristic based

process/standard-compliant - adopt an industry-standard, agile methodologies

reactive - reactive to the component or system, exploratory testing

directed/consultative - driven by the guidance/instructions of stakeholders/technology experts, ask users/developers

regression-averse - automate tests


Factors For Defining The Strategy: risks, available resources, test objectives, regulations, the nature of the product, safety, technology;


Test Plan: component test plan, integration test plan, system test plan, acceptance test plan


Entry Criteria (Definition Of Ready - DOR):

- availability of testable requirements 

- availability of test items 

- availability of test environment 

- availability of test tools

- availability of test data

 

Exit Criteria (Definition Of Done - DOD):

- planned tests executed

- defined level of coverage achieved

- number of unresolved defects is within the defined limit

- evaluated levels of quality characteristics


Test Estimation:

- metric-based (based on statistics in a similar project),

- expert-based (business experts, consultants, developers)


Test reports: test progress reports, test summary reports