[ISTQB] 5.2 Test Planning and Estimation (K3)

LO-5.2.1 Recognize the different levels and objectives of test planning (K1)

Test approach is the implementation of the test strategy for a specific project and typically includes the decisions made that follow based on project's goals and the risk management carried out. 

Test planning is the first stage in test process, it defines the scope of testing and the test completion criteria which determine when we stop to test. It covers development, implementation projects and maintenance activities and is influenced by project organization. (risk analysis performed) 

A high level project test plan could then divided in 5 test plans for each level of testing: acceptance, system integration, system, component integration, component. 

LO-5.2.2 Summarize the purpose and content of the test plan, test design specification and test procedure documents according to the 'Standard for Software Test Documentation' (IEEE Std 829-1998) (K2)

At the test planning stage, test plan is needed and according to the ISTQB definition, it's "a test plan is document describing the scope, approach, test objectives, constraints (resources and schedule of testing activities). It describes the feature to be test, the testing tasks, responsibilities, the degree of testing independence, the testing environment required, test design techniques and test measurement used, and any testing risks requiring contingency planning."

At test specification stage, test design specification, test case specification, test procedure specification and test item transmittal report are expected.

At test execution stage, test log, test incident report and test summary report are expected. 

LO-5.2.3 Differentiate between conceptually different test approaches, such as analytical, model-based, methodical, process/standard compliant, dynamic/heuristic, consultative and regression-averse (K2)

Test approach defines how testing is going to be planned, designed, and implemented and is adjusted with regards to project's context, risks, resources available and nature of the system.

• analytical approach: based on a risk based analysis.
• model-based approach: based on statistical information and operational profile.
• methodical approach: where there is no test basis, is based of experience, checklists and quality characteristics.
• process/standard compliant approach: is based on industry standards and agile methodologies if applicable (SCRUM and prototypes).
• dynamic/heuristic approach: in AGILE methodology, this approach is based on exploratory testing, re-viewable results and heuristics.
• consultative and regression-averse: an expert is highly involved in consultative and in regression approach, tests are essentially automated and used to confirm that no defect has been introduced for confirming product's quality. 

LO-5.2.4 Differentiate between the subject of test planning for a system and scheduling test execution (K2)

• Test planning is a continuous activity, performed in all life cycle processes and activities. Test scheduling is prepared after determining scope, risks, test objective, test approach, test levels, entry/exit criteria, resources needed, constraint and has to take in account its integration in the software life cycle. 
• Test scheduling includes preparing when, how long and by who test analysis, design, implementation, execution and evaluation will be performed.
• Test execution schedule needs to address prioritization, technical and logical dependencies. (test sequence) 

LO-5.2.5 Write a test execution schedule for a given set of test cases, considering prioritization, and technical and logical dependencies (K3)


LO-5.2.6 List test preparation and execution activities that should be considered during test planning (K1)


LO-5.2.7 Recall typical factors that influence the effort related to testing (K1)

Test planning facilitates testing effort analysis. However, it relies upon product's characteristics such as: product's size and complexity, test basis quality and availability (requirements, specifications), security and reliability requirements. 

Additionally, characteristics of development's process can influence effort testing like organisation stability, tools used and skills required, time pressures. 

LO-5.2.8 Differentiate between two conceptually different estimation approaches: the metrics-based approach and the expert-based approach (K2)

Estimations are required for appreciating how long each testing phase (test planning, test analysis, test design, test execution and evaluation) would take. It aims to determine test effort required.

• Metrics-based approach is based on experience and use consequently metrics of former/similar projects or tasks.
• Expert-based approach is based on the estimation give by the owner of the task or an expert.(personal opinion) 

LO-5.2.9 Recognize/justify adequate entry and exit criteria for specific test levels and groups of test cases (e.g., for integration testing, acceptance testing or test cases for usability testing) (K2)

• Entry criteria avoid wasting testing effort and precise when testing can start, once typically environment, tools, testable code and data are available, 
• Exit criteria (usually a coverage stated and influenced by test budget, residual risks and schedules) contributes to a clear understanding of when the test should stop and should therefore measurable.