Monday, 1 December 2014

Testing plan is a methodological & systematical approach to testing a system such as a machine & software. Test plan can be effective in finding the errors & flaws in a system. In order to find the relevant outcomes, a plan typically contains the experiments with a range of operations & values, involving an understanding of what eventual workflows will be. A test plan is a document which involves introduction, list of test cases, assumptions, & the list of features to be tested, deliverables, approach, resources, risks & scheduling.
In the software testing term, the test plan gives the detailed testing information’s about an upcoming testing effort, involves:
1.       Scopes of testing
2.       Test Deliverable
3.       Schedules
4.       Risks & Contingencies
5.       Release Criteria’s
Essential Clauses of your Test Plan
1.       An Introduction:
An Introduction is a section that usually contains overall information regarding test plans & testing activity. It involves the schedules of testing, intermediate goals or all the documentation concerns the QA projects.

2.       Set of the authorized persons:
This section you must point out the all peoples that are authorized user to entrance to this test plan & to locate place where these documents will be kept.

3.       Software’s testing background:
Occasionally testing is carried out with affords of many development teams which are not interacting with to each other. I.e. why test plan must contains the all information’s regarding development activity, test-strategies that are recommended, or the activities achieved & so on to provide to each team with all necessary information.

4.       Schedules:
In the section, you should specify the dead-lines or a milestone of all of your testing works.

5.       resources are engaged:
 This section should contain the needs of software’s, hardware’s or testing tools resources. The unbiasedness (objectiveness) of this information is of the great importance, because a lack of resources might cause a complete termination of the development project.

6.       Features to be & not to be tested:
In this block you should specify the software elements that’s are to be tested & that are not to be tested as well as in order to avoid the double testing caused through the implementation of the third party software. Also you should points out your testing strategies here which involves to all types of testing that are supposed to be carried out.

7.       Controlling or Monitoring:
In this block you should specify the form of problems reporting or point out changes that might be provided or by what means.

8.       Deliverables or Items:
Both of these two components of the test plans are essential to be specified. Usually simple list of testing items or deliverables compared with the time frames will complete.

9.       Risks or Contingencies:
In this part it is dedicated to detailed contingency plans.
Contingency plan means, the contingency plan is the plan that devised for a result other than in usual (expected) plans.

10.   Approvals:

This is a final section it involves a list of the peoples who have approve this test plan.

0 comments:

Post a Comment

Bookmark Us

Delicious Digg Facebook Favorites More Stumbleupon Twitter