5.1 Test Planning

5.1.1 Purpose and Content of a Test Plan

FL-5.1.1 (K2) Exemplify the purpose and content of a test plan

A test plan describes the test objectives, resources and processes for a test project. A test plan:

• Demonstrates that testing will adhere to the existing test policy and test strategy (or explains why the testing will deviate from them)
• Documents the means and schedule for achieving test objectives
• Helps to ensure that the performed test activities will meet the established criteria
• Serves as a means of communication with team members and other stakeholders

5.1.2 Tester’s Contribution to Iteration and Release Planning

FL-5.1.2 (K1) Recognize how a tester adds value to iteration and release planning

In iterative SDLCs, typically two kinds of planning occur: release planning and iteration planning.

5.1.3 Entry Criteria and Exit Criteria

FL-5.1.3 (K2) Compare and contrast entry criteria and exit criteria

Entry criteria define the preconditions for undertaking a given activity. If entry criteria are not met, it is likely that the activity will prove to be more difficult, time-consuming, costly, and riskier. Exit criteria define what must be achieved to declare an activity completed. Entry criteria and exit criteria should be defined for each test level, and will differ based on the test objectives.

5.1.4 Estimation Techniques

FL-5.1.4 (K3) Use estimation techniques to calculate the required test effort

Test effort estimation involves predicting the amount of test-related work needed to meet the test objectives of a test project. It is important to make it clear to the stakeholders that the estimate is based on a number of assumptions and is always subject to estimation error. Estimation for small tasks is usually more accurate than for the large ones. Therefore, when estimating a large task, it can be decomposed into a set of smaller tasks which then in turn can be estimated.

5.1.5 Test Case Prioritization

FL-5.1.5 (K3) Apply test case prioritization

Once the test cases and test procedures are specified and assembled into test suites, these test suites can be arranged in a test execution schedule that defines the order in which they are to be run. When prioritizing test cases, different factors can be taken into account. The most commonly used test case prioritization strategies are as follows:

• Requirements-based prioritization
• Risk-based prioritization
• Coverage-based prioritization

5.1.6 Test Pyramid

FL-5.1.6 (K1) Recall the concepts of the test pyramid

The test pyramid is a model showing that different tests may have different granularity. The test pyramid model supports the team in test automation and in test effort allocation by showing that different test objectives are supported by different levels of test automation.

5.1.7 Testing Quadrants

FL-5.1.7 (K2) Summarize the testing quadrants and their relationships with test levels and test types

The testing quadrants group the test levels with the appropriate test types, activities, test techniques and work products in the Agile software development.

The model supports test management in visualizing these to ensure that all appropriate test types and test levels are included in the SDLC and in understanding that some test types are more relevant to certain test levels than others. This model also provides a way to differentiate and describe the test types to all stakeholders, including developers, testers, and business representatives.