p.

Test Plan Template

Author:
Test Plan Template................................................................................................................
Objective................................................................................................................................
Scope......................................................................................................................................
Test approach.........................................................................................................................
Entry criteria..........................................................................................................................
Exit criteria............................................................................................................................
Risks/Assumptions................................................................................................................
Defect management...............................................................................................................
Test Deliverables...................................................................................................................
Schedule.................................................................................................................................
Resources...............................................................................................................................
References..............................................................................................................................

Introduction
Give an overview of the release and it's objective.

Objective
Describe the objective of the testing exercise - what is intended to be achieved.

Scope
Describe the scope / limitations of this testing exercise. Describe what will be tested and what
will not be tested.

Features to be tested
....
....
....

Features not to be tested

....
....
....

Test approach
Describe the approach you adopt to complete testing for this release. Mention if you are going
to do a full fledged testing or running a minimum number of tests depending on the release
requirements. Minimum acceptace, functionality, browser compatibility, integration,
end-to-end, load, adhoc tests, etc. If testing is done across different phases, please mention here.

Entry criteria
Define requirements to be fulfilled before starting testing. You can describe entry criteria for
each type of testing required to perform.
Example: For commencing integration testing of the Drupal CMS with your organizations
website, basic functionality of Drupal, and the points of integration from your organizations
website should be available which allows them to talk to each other.

p.3

Exit criteria
Define the exit criteria which mark the end of testing for the release. This can also be defined for
each type of testing required to complete.
Example: No P1 bugs should be open.
If you would like to understand more about bug classification (bug severity and bug priority,
visit http://www.softwaretestingconcepts.com/bug-classification-based-on-severity-and-priority

Risks/Assumptions
The following are only examples. Modify appropriately
Test deliverables (schedule) can be affected:
If module is not delivered on time which pushes the test start date
If prioritized bugs are not fixed in time
Necessary hardware resources are unavailable at the time of testing
Team members leave the project or are pulled into another high priority task as felt
necessary by Sponsors

Defect management
Bugs encountered during the testing process will be filed in <Name of Bug tracking tool>
available at url:
http://<web location of bug tracking tool>

Test Deliverables
The following is an example only. Please modify appropriately.
Test Plan (this document)
Test Cases
Test Scripts in Python to run the tests
Testing status reports will be sent to stake holders over email twice a week/weekly. Issues
will be highlighted and discussed on the conference calls.
Defect Reports & Matrices

 Final Test Completion Report with release recommendation

Schedule
Describe the testing activity schedule. Reference the source of information based on which the
dates were arrived at.
The following is an example only. Please modify appropriately.
Deliverable

Expected Start Date

Minimum Acceptance Tests

16th June 2008

Expected End Date

System testing
Integration testing

Resources
Hardware
QA Machine configuration details (Example: testing content management system Drupal)
Machine configuration based on deployment plans (Example: what is required to run Drupal for
Windows, Linux, etc)

Software
OS requirements
Packages and tools required

People
The following are only examples. Please modify appropriately.
Team member

Responsibility

<Team Lead Name>

Planning, test execution, reporting and sign off

<Member1 Name>

Test cases, test execution, reporting

<Member2 Name>

Test cases, test execution, reporting

p.5

References
The following are only examples. Please modify appropriately.

http://en.wikipedia.org/wiki/Content_management_system

http://www.opensourcecms.com/