Test Plan document in IEEE Format
Written by Thong D. Nguyen Sunday, 27 March 2011 15:22
Reference - Software Testing
- Test Plan ID: Unique No. or Id or Name of the test plan
- Introduction: About the Project and testing
- Test Items: Names of Modules/ Functions/ Services/ Features
- Features To Be Tested: Responsible Modules for the Test Design
- Features Not To Be Tested: Which ones to test and which ones not to test (e.g. Features of previous version of the Software)
- Approach: List of testing techniques to be applied on the modules (prepared by QA/PM)
- Features Pass/Fail Criteria: When above features are pass and when they fail
- Suspension Criteria: Possible abnormal situations arose during testing of above features. Without recovering from these situations, you are not able to conduct testing. (Technical problems with respect to project)
- Test Environment: Required hardware and software including testing tools to conduct testing
- Test Deliverables: Required test documents to be prepared during testing (Test Cases, Test Procedures, Test Log, Test Report)
- Test Tasks: necessary tasks to do before starting of every project testing
- Staff and Training Needs: The names of test engineers and required training sessions
- Responsibilities: Work allocation in terms of test engineers Vs Modules
- Schedule: Dates and Times
- Risks and Mitigations: Analyze risks and possible solution to overcome them
- Approvals: Signatures of Test Plan Author and PM/QA
| < Prev | Next > |
|---|
Idioms
- When is Rome, do as the Romans do. (Nhập gia tùy tục)
- Grasp all, lose all. (Tham thì thâm)
Who's online
We have 6 guests online
Location
38.107.179.217
38.107.179.217Search Bot
unknown unkno

OS
PHP
MySQL
Time
Caching
GZIP
Members
Content
Web Links




Today
Yesterday
This week
Last week
This month
Last month
All days