Topic: Acceptance Test Plan {ATP}

Message

   Acceptance Test Plan {ATP}
The
client at their place performs the acceptance testing. It will be very
similar to the system test performed by the Software Development Unit.
Since the client is the one who decides the format and testing methods
as part of acceptance testing, there is no specific clue on the way
they will carry out the testing. But it will not differ much from the
system testing. Assume that all the rules, which are applicable to
system test, can be implemented to acceptance testing also.

A sample Test Plan Outline along with their description is as shown below:

Test Plan Outline 
1.   BACKGROUND – This item summarizes the functions of the application system and the tests to be performed.
2.   INTRODUCTION 
3.   ASSUMPTIONS – Indicates any anticipated assumptions which will be made while testing the application.
4.   TEST ITEMS - List each of the items (programs) to be tested.
5.   FEATURES
TO BE TESTED - List each of the features (functions or requirements)
which will be tested or demonstrated by the test.
6.   FEATURES NOT TO BE TESTED - Explicitly lists each feature, function, or requirement which won't be tested and why not.
7.   APPROACH - Describe the data flows and test philosophy.
Simulation
or Live execution, Etc. This section also mentions all the approaches
which will be followed at the various stages of the test execution.
8.   ITEM PASS/FAIL CRITERIA Blanket statement - Itemized list of expected output and tolerances
9.   SUSPENSION/RESUMPTION CRITERIA - Must the test run from start to completion?
Under what circumstances it may be resumed in the middle?
Establish check-points in long tests.
10.   TEST DELIVERABLES - What, besides software, will be delivered?
Test report
Test software
11.   TESTING TASKS Functional tasks (e.g., equipment set up)
Administrative tasks
12.   ENVIRONMENTAL NEEDS
Security clearance
Office space & equipment
Hardware/software requirements
13.   RESPONSIBILITIES
Who does the tasks in Section 10?
What does the user do?
14.   STAFFING & TRAINING
15.   SCHEDULE
16.   RESOURCES
17.   RISKS & CONTINGENCIES
18.   APPROVALS 
The
schedule details of the various test pass such as Unit tests,
Integration tests, System Tests should be clearly mentioned along with
the estimated efforts. 

Author	Message
tanushree Senior Member Joined: 04Apr2007 Online Status: Offline Posts: 2160	Topic: Acceptance Test Plan {ATP} Posted: 15Oct2007 at 4:14am
	Acceptance Test Plan {ATP} The client at their place performs the acceptance testing. It will be very similar to the system test performed by the Software Development Unit. Since the client is the one who decides the format and testing methods as part of acceptance testing, there is no specific clue on the way they will carry out the testing. But it will not differ much from the system testing. Assume that all the rules, which are applicable to system test, can be implemented to acceptance testing also. A sample Test Plan Outline along with their description is as shown below: Test Plan Outline 1. BACKGROUND – This item summarizes the functions of the application system and the tests to be performed. 2. INTRODUCTION 3. ASSUMPTIONS – Indicates any anticipated assumptions which will be made while testing the application. 4. TEST ITEMS - List each of the items (programs) to be tested. 5. FEATURES TO BE TESTED - List each of the features (functions or requirements) which will be tested or demonstrated by the test. 6. FEATURES NOT TO BE TESTED - Explicitly lists each feature, function, or requirement which won't be tested and why not. 7. APPROACH - Describe the data flows and test philosophy. Simulation or Live execution, Etc. This section also mentions all the approaches which will be followed at the various stages of the test execution. 8. ITEM PASS/FAIL CRITERIA Blanket statement - Itemized list of expected output and tolerances 9. SUSPENSION/RESUMPTION CRITERIA - Must the test run from start to completion? Under what circumstances it may be resumed in the middle? Establish check-points in long tests. 10. TEST DELIVERABLES - What, besides software, will be delivered? Test report Test software 11. TESTING TASKS Functional tasks (e.g., equipment set up) Administrative tasks 12. ENVIRONMENTAL NEEDS Security clearance Office space & equipment Hardware/software requirements 13. RESPONSIBILITIES Who does the tasks in Section 10? What does the user do? 14. STAFFING & TRAINING 15. SCHEDULE 16. RESOURCES 17. RISKS & CONTINGENCIES 18. APPROVALS The schedule details of the various test pass such as Unit tests, Integration tests, System Tests should be clearly mentioned along with the estimated efforts. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Test Plans @ OneStopTesting