Test in practice

1. Introduction and Feature Description

2. Assumption(Scope)

3. Test Approach

4. Test Suite Structure

5. Test Environment

6. Test Execution Strategy

7. Test Effort Estimation

8. Scheduling and Milestones

summarize the system features that will be tested during the execution of this plan

Areas for which test cases will and will not be designed

In Scope (Inclusion items) Out Of Scope (Exclusionitems)

Which types of tests will be run. Automation level, special focus for specific issues.

• a test suit is a bucket that holds a collection of test cases with similar behaviors or goals

• are usually created by grouping test cases relating to a requirement

• plan for creation of test environments

• multiple environments can be needed to specific tests such as security and scalability

• specific hardware, third party tools, test data

conditions for prematurely terminating a test cycle and for extending a test cycle must be precisely stated

• Priorization of the test execution changes between test cycles

• each cycle must come to an end and shall have exit criteria

… too many test cases may fail during a test cycle

-> the system test team has to design a large number of new test cases during a test cycle

Effort required to:

• create a detailed test case

• executre a test case and analyze the results of execution

• create the test environments

• report the defects

• reproduce the failure

• follow up with development temas

• usually simplistically represented by a statetransition diagram with five states

• new, assigned, open, resolved, closed

processes of

• test case execution

• tracking defects

• measure test effectiveness