Saturday, January 24, 2015

IEEE 829 Testplan format

Subscribe To get updates

Enter your email address:


Delivered by Mindq Software Testing Tutorials

Test plan:

Test plan ID: It should be unique ID for future reference
Introduction: It includes brief description about the project.
Test Item: List of modules in project.
Feature to be tested: In this we can consider list of modules/functionalities  that are need to  test
Feature not to be tested: List of modules, which are already tested in previous version
Approach:-List of testing technique to be applied on modules ( from test strategy)
Test deliverables: Required testing documents to be prepared by testing team. Test deliverables include the following
--> Test strategy
--> Test plan
--> Test Scripts
--> Test summery report
-->  Test case document
-->  Test scenarios documents
-->  Requirements Traceability matrix
--> Bug/issue report
--> Test results
Test environment: Required H/W, S/W to test modules.
Entry criteria: Quality  Engineer are able to start test execution after creating as
  1. Test cases develop & review
  2. Test environment established
  3. S/W build received from development.
Suspension criteria: Same times test engineer stop test execution. Due to
a. Testing environment is not working.
b. Reported defects are more at development side in other
Exit criteria: It defines test execution process exit point.





















 

No comments:

Post a Comment