Test Planning

Sponsored Links:

A document that describes the scope, approach, resources and schedule of activities planned test. They identify the evidence, the characteristics of the test, the testing tasks, who will do each task, and any risks requiring contingency plans.

Test Plan Template :
1)Introduction
2)Items to be Tested
3)Features to be Tested
4)Approach
5)Pass/Fail Criteria
6)Suspension and Resumption Criteria
7)Test Deliverable
8)Testing Tasks
9)The Testing Environment
10)Responsibilities
11)Staffing and Training Needs
12)Scheduling
13)Risks and Contingencies
14)Approvals

Summarize the elements of software and software features to be tested. The need for each item and its history can be included.
References to the following documents, when available, are needed at the highest level plan of the test:
1) the consent
2)The project plan
3) Quality Assurance Plan
4) Configuration Management Plan
5)relevant policies
6)The relevant rules 

Test Items:
Identify the evidence, including their version / revision level.
References to supply the following documentation of test item, if any:
1) specification of requirements
2)Design specification
3) providing guidance to users
4) Operations Guide
And Installation Guide
Reference to any incident reports relating to evidence.
The articles are to be specifically excluded from the tests can be identified .

Features to be tested:
Identify all software features and combination of software features to be tested. Identify the type of test specifications associated with each function and each combination of characteristics.

Features not to be tested:
Identify all features and combination of important features that will be tested and why.

Approach:
1)Describe the overall approach to testing. For each major group of features or combinations of features
2)Specify the method of ensuring that these groups are adequately tested function.
3)Specify the major activities, techniques and tools that are used to test the designated groups of features.
4)The approach should be described in sufficient detail to permit identification of the major testing tasks and estimation of time required to make each one.
5)Specify the minimum degree of comprehensiveness. Identify the techniques used to assess the extent of the testing effort (eg, determining which states have been executed at least once).
6)Specify any additional completion criteria (for example, the frequency of error). The techniques used to trace the requirements to be determined.
7)Identify significant constraints on testing such as test item availability, testing resource availability and deadlines.

Item pass/fail criteria:
Specify the criteria used to determine whether each test item has passed or failed the test .

Suspension criteria and resumption requirements:
1)Specify the criteria used to suspend all or part of the testing activity on the evidence related to this plan.
2)Specify control activities that must be repeated when the trial resumed.


Test deliverable:
Identify documents to be delivered. The documents should include:
1) test plan;
2)design specifications
3) Analysis;
4)specifications case
5) Evidence;
6)procedure specifications
7) examination;
8)transmission reports
9) test point (test item presented Eng)
10) Test incident reports;
11) summary reports of the test.
Test data input and output test data should be identified as the final results.
Test tools (eg, module drivers and heels) may also be included.

Testing tasks:
Identify all the tasks necessary to prepare and conduct the tests. Identify all task interdependencies and special skills needed.

Environmental needs:
Specify both the necessary and desired properties of the test environment. This specification should include the physical characteristics of facilities,including hardware, communications and system software, how to use (eg, stand-alone), and any other software or supplies needed to support the test.Specify the level of security to be provided for testing facilities, software components and owners as software, data and hardware.Identify special test tools required. Identify the needs of other evidence (eg, publications or office space). Identify the source for all needs that are not currently available to the test group.

Responsibilities:
1)Identify the groups responsible for the management, design, preparation, execution, witness, verify and resolve.
2)Identify the groups responsible for providing the evidence found and the environment identified needs.
3)These groups may include developers, testers, operations staff, user representatives, technical support personnel, data management staff and support staff quality.

Staffing and training needs:
Specify staffing needs by testing the level of skill. Identify training options for providing the necessary skills.

Schedule:
1)Include test milestones identified in the software project schedule and all transmission events topic.
2)Defining additional test milestones needed. Estimate the time required to complete each task of the test.
3)Specify the schedule for each task, trial and a landmark trial. For each testing resource (ie, facilities, tools, and staff)
specify its periods of use .

Risks and contingencies:
Identifying high-risk cases that the test plan. Specify contingency plans for delivery of each (eg, the backlog of evidence might require increased night shift schedule to meet the delivery date).