Monday, June 15, 2009

What is Test Plan


Test plan :-
-------------
Test plan is a Document,which describes the scope, approach and schedule of testing activities or we can say "What to Test","How to Test", "When to Test", "Who to Test".It is the responsibility of test lead to develop this document.
Scope of testing
Testing approach
Time frame
Objectives of testing
What will be the environment
Risk factors

1.Risk Identification[conducts risk identification meetings]
2.Risk Analysis [Categorizing Risk]
3.Risk Response planing [next plan mitigation activities, contingency activities, and review the risk action plans]
4.Risk Plan implementation [once these are established, monitor trigger events, execute the action plan, and update the Risk Log.]
5.Risk Tracking, Monitoring & Control [this stages concerns how the risk is progressing, as well as mitigation/contingency strategies that have been executed. When changes to the risk occur, repeat the cycle of identify, analyze, and plan]
Features to be tested
Features not to be tested.
Roles and Responsibilities
Entry and Exit Criteria
Entry

1.All requirements and design documentation is subjected to management and peer review, accepted and in final form, and placed under configuration management control
2.All test plans and test cases are complete, subjected to management and peer review, accepted and in final form, and placed under configuration management control
3.All defects identified during unit testing have been fixed prior to integration and system testing or should be detailed in release notes
4.All necessary test environment hardware, software and test tools are complete and the staging environment is configured to appropriately mirror the production environment
Exit
The following are the requirements, which must be satisfied prior to formal exit
from system testing:
1.All test cases were successfully completed
2.Regression testing is complete and successful
3.All critical or major-priority defects are resolved and closed and all remaining open defects are reviewed by project team for potential impact, and formally waived or deferred as deemed appropriate
4..All test deliverables completed
Suspension criteria
The test cases for each level must be run successfully before the next level of testing begin. If an error is discovered, testing will be halted until the developers fix the error. Mention other situations when the testing may need to be halted.
Server is down and not responding Server is down and not responding
Home page is in accessible or will not load in browser
Major component of the site will not execute
Any critical defect is identified that will impede the execution of test cases
Staffing and Training Needs
Test Deliverable
Test plan
Test case documentation
Test Execution Report
Defect reports
Traceability matrix

No comments:

Post a Comment