Interested to Buy Any Domain ? << Click Here >> for more details...
What is a Test Plan and What it contains?
- 2 Answers
- 9197 Views
- Virtusa, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / shailu
A software project test plan is a document that describes
the objectives, scope, approach, and focus of a software
testing effort. It should be thorough enough to be useful
but not so thorough that no one outside the test group will
read it. The following are some of the items that might be
included in a test plan, depending on the particular
project:
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.
| Is This Answer Correct ? | 3 Yes | 0 No |
How will you recognise if a case is a 'test case'?
What is heuristics testing?
What is the difference between Manual Test Plan and the Automated Test Plan?
What is the difference between Testing and Code review?
What is difference between Agile and V model? Explain
What is depth testing?
Hi I am newly joined this forum.I am from Uk coming to hyderabad for 8 weeks for Software Testing Course.Please advice me the best Institute. Eagerly waiting for your response ASAP.
Explain 'Software metrics'?
What is different Between Black boxtesting and functional testing...
Explain test driver?
Hi, I don't know exactly when System Testplan should be prepared 1)while analysing BRS or 2) analysing FRS or 3) after analysing the Requirement Specification
Which one of the following is used as a tool for tracking an SQA project? 1. Pareto chart 2. PERT chart 3. Run chart 4. Control chart 5. Cause and effect chart
Automation Testing 
