Test Plan in software Testing |Definition , Activities etc

Test Plan Activities

• • • Test Plan Activities determine the scope and risks that need testing, involve the Project Manager
    • Identify and agree on the objectives of testing, with a focus on TIME, QUALITY and COST.
    • A Test Strategy (Overall Approach) ensures that test levels, entry criteria and exit criteria are defined
    • Making decisions
      • Features to test?
      • What roles will perform the testing activities?
      • When and how the testing activities should be done?
      • How the test results will be evaluated?
      • Exit criteria
    • Create a Plan to identify when and who will undertake the test analysis and design activities along with the documentation of the schedule for test implementation, test execution and test evaluation
    • Decide on the format of test project documentation, and which plans and test cases will be documented.
    • Define Management information including the metrics required, establishing processes to monitor and control test preparation and execution along with defect resolution and risk issues.
    • Ensure that test documentation generates test assets i.e. test cases.

ENTRY CRITERIA

• • • Entry Criteria in Test Plan defines when to start testing
    • Can include the start of a level of testing, start of test design and/or start of test execution.
    • The stages of Entry Criteria to Test Execution are as follows:
      • Test tools installed in the environment which should be ready for use.
      • Testable code is available.
      • All test data is available and correct.
      • All test design activity has completed.

EXIT CRITERIA

• • • Exit Criteria in Test Plan is used to decide when a test activity has been completed or needs to stop.
    • Exit Criteria can be defined for all test activities such as planning, specification and execution or for a specific test level for test specification and execution.
    • Exit Criteria should have been agreed as early as possible in the life cycle.

Typical exit criteria are:

• • • Estimates of defect density or reliability measures
    • Functionality or risk
    • Thoroughness measures, such as coverage of code,
    • Residual risks, such as defects not fixed or lack of test

Test plan includes the following components:

Introduction:
This section provides an overview of the testing process, including the scope, objectives, and approach.

Test Objectives:
This section outlines the goals and objectives of the testing process, including the expected outcome of the testing.

Testing Scope:
This section defines the scope of the testing process, including the features and functionalities to be tested, the types of testing to be conducted, and the testing environment.

Testing Approach:
This section outlines the testing approach to be used, including the testing techniques, tools, and methods.

Test Schedule:
This section outlines the timeline for the testing process, including the testing phases, milestones, and deadlines.

Test Deliverables:
This section defines the deliverables of the testing process, including the test plan document, test cases, test scripts, and test reports.

Test Environment:
This section describes the testing environment, including the hardware, software, and network configurations.

Roles and Responsibilities:
This section outlines the roles and responsibilities of the testing team members, including the test manager, test analysts, and testers.

IEEE-829 Test Plan

1. 1. TestPlan Identifier
   2. References
   3. Introduction
   4. Test Items
   5. Software Risk Issues
   6. Features to be Tested
   7. Features not to be Tested
   8. Approach
   9. Item Pass/Fail Criteria
   10. Suspension Criteria and Resumption
   11. Requirements
   12. Test Deliverables
   13. Remaining Test Tasks
   14. Environmental Needs
   15. Staffing and Training Needs
   16. Responsibilities
   17. Schedule
   18. Planning Risks and Contingencies
   19. Approvals
   20. Glossary

SPACE DIRT = IEEE829 TestPlan

S – Scope test items, what to test, what not to test

P – People training, responsibilities, schedule

A – Approach the approach that will be taken to testing

C – Criteria entry/exit criteria, suspension/resumption criteria

E – Environment test environment needs

D – Deliverables what is being delivered as part of the test

process

I – Incidentals introduction, identification (of the document),

approval authorities

R – Risks risks and contingencies

T – Tasks the test tasks that are involved in the testing

process.

Recommended Articles:  

• • • Test Strategies Vs Test Plan
    • Test Approaches
    • Risk and Testing
    • Product Risks
    • Project Risks
    • Defect Management