Test Plan

What are the key components of Test Plan Document?

Replies to This Discussion

Permalink Reply by nprajapati on March 26, 2010 at 11:15am

The Key components are

1. Availability of test engineers
2. Availability of test resources (like hardware etc)
3. Test duration
4. Types of Testing
5. Nature of testing (on site or offshore)
6. Manual testing details
7. Automation test details
8. Lack of resources.
9. Time schedule.

Regards.
Nimesh Prajapati

▶ Reply

Permalink Reply by Somanathan on March 26, 2010 at 11:22am

For more details, pls refer this link.

http://it.toolbox.com/blogs/enterprise-solutions/testing-a-sample-t...

Regards,
Somanathan R.

▶ Reply

Permalink Reply by nprajapati on March 26, 2010 at 11:23am

Thank you Somanathan R.

Regards,
Nimesh Prajapati

▶ Reply

Permalink Reply by Anil Babu on March 26, 2010 at 11:33am

Hi,
1.Test Plan Id.
2.Introduction.
3.Features to be Tested
4.Features not to be Tested:
5.Test Items:
6.Suspension Criteria
7.Features Pass/Fail Criteria
8.Test Environment.
9.Test Deliverables.
10.Test Approach.
11.Testing Tasks
12.Staff and Training Needs
13.Roles and Responsibilities.

▶ Reply

Permalink Reply by Himanshu Patel on March 26, 2010 at 11:44am

Refer to the following link(s):

- http://www.sqatester.com/documentation/testplansmpl.htm
- http://en.wikipedia.org/wiki/Test_plan
- http://bazman.tripod.com/frame.html

Regards,
Himanshu Patel

▶ Reply

Permalink Reply by nprajapati on March 26, 2010 at 12:07pm

Thanks Mr. Patel

Regards,
Nimesh Prajapati

▶ Reply

Permalink Reply by nprajapati on March 30, 2010 at 12:57pm

* Title
* Identification of software including version/release numbers
* Revision history of document including authors, dates, approvals
* Table of Contents
* Purpose of document, intended audience
* Objective of testing effort
* Software product overview
* Relevant related document list, such as requirements, design documents, other test plans, etc.
* Relevant standards or legal requirements
* Traceability requirements
* Relevant naming conventions and identifier conventions
* Overall software project organization and personnel/contact-info/responsibilties
* Test organization and personnel/contact-info/responsibilities
* Assumptions and dependencies
* Project risk analysis
* Testing priorities and focus
* Scope and limitations of testing
* Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable
* Outline of data input equivalence classes, boundary value analysis, error classes
* Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems
* Test environment validity analysis - differences between the test and production systems and their impact on test validity.
* Test environment setup and configuration issues
* Software migration processes
* Software CM processes
* Test data setup requirements
* Database setup requirements
* Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs
* Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs
* Test automation - justification and overview
* Test tools to be used, including versions, patches, etc.
* Test script/test code maintenance processes and version control
* Problem tracking and resolution - tools and processes
* Project test metrics to be used
* Reporting requirements and testing deliverables
* Software entrance and exit criteria
* Initial sanity testing period and criteria
* Test suspension and restart criteria
* Personnel allocation
* Personnel pre-training needs
* Test site/location
* Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues
* Relevant proprietary, classified, security, and licensing issues.
* Open issues
* Appendix - glossary, acronyms, etc.

▶ Reply

Permalink Reply by Hitesh Shah on March 30, 2010 at 2:32pm

Hi, nice , I want to know about Test Scope description with example

Thanks

▶ Reply

Permalink Reply by vishnu chaudary on March 31, 2010 at 10:20am

Hitesh! Test scope depends on the scalability of the product.I mean to say where there is/will be a chance to include more enhancements and features...