ctsprachi

 Profile Answers by ctsprachi 

• Jun 30th, 2010

 

Test Plan is a document which specifies the entire Planning of the Software Testing Project. It includes:

1. Sope of Tesing
2. Approach to be followed
3. Risk Issues and Mittigations
4. Resource Information
5. Modules to be covered.

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Jul 14th, 2010

 

A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A test plan is usually prepared by or with significant input from Test Engineers

1. Scope
2. Testing Approach
3. Testing Procedure
4. Risks and contingencies
5. Resources (Man & System) & Training needs
6. Test Coverage
7. Test Deliverables
8. Testing Tasks
9. Responsibilities
10. Approvals

ravisql

 Profile Answers by ravisql 

• Jul 19th, 2010

 

Test Plan contains

Objective

Scope

Approach

Deliverables

Graphs and Matrix

Assumption

Risk

Contingency plan

Effort estimation

Entry and Exit Criteria

Test Automation

Test Environment

Defect Tracking

Schedule

Templates

kamalakar2000

 Profile Answers by kamalakar2000 Questions by kamalakar2000

• Jul 24th, 2010

 

A Test plan contain following these:

1) Test plan identifier
2) Introduction
3) Test items
4) Features to be tested
5) Features not be tested
6) Approach
7) Item pass or fail criteria
8) Suspension and resumption criteria
9) Test deliverable
10) Test tasks
11) Test environment
12) Responsibilities
13) Stab training needs
14) Schedule
15) Risk management
16) Approval

vishnu.p

 Profile Answers by vishnu.p 

• Aug 3rd, 2010

 

Explain test plan content: Test Plan is a document which specifies the entire Planning of the Software Testing Project.

It includes:
Objective
Scope
Approach
Deliverables
Assumption
Resources (Man & System) & Training needs
Effort estimation
Entry and Exit Criteria
Test Automation
Test Environment
Defect Tracking
ScheduleTemplates

saritha1406

 Profile Answers by saritha1406 

• Nov 1st, 2010

 

A software project test plan is a document that describes the objectives, scope,

approach, and focus of a software testing effort.
The following are some of the items that might be included in a test plan, depending on the particular project:

1)Title

2)Identification of software including version/release numbers

3)Revision history of document including authors, dates, approvals

4)Table of Contents

5)Purpose of document, intended audience

6)Objective of testing effort

7)Software product overview

8)Relevant related document list, such as requirements, design documents, other test plans, etc.

9)Relevant standards or legal requirements

10)Traceability requirements

11)Relevant naming conventions and identifier conventions

Overall software project organization and personnel/contact- info/responsibilities

Test organization and personnel/contact-info/responsibilities

12)Assumptions and dependencies

13)Project risk analysis
14)Testing priorities and focus

15)Scope and limitations of testing

16)Test outline - a decomposition of the test approach by test type, feature,

functionality, process, system, module, etc. as applicable

17)Outline of data input equivalence classes, boundary value analysis, error classes

18)Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems

19)Test environment validity analysis - differences between the test and production systems and their impact on test validity.

20)Test environment setup and configuration issues Software migration processes

21)Test data setup requirements

22)Database setup requirements

23)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

24)Test automation - justification and overview

25)Test tools to be used, including versions, patches, etc.

26)Test script/test code maintenance processes and version control

27)Problem tracking and resolution - tools and processes

28)Project test metrics to be used

29)Reporting requirements and testing deliverables

30)Software entrance and exit criteria

31)Initial sanity testing period and criteria

32)Test suspension and restart criteria

33)Personnel allocation

34)Personnel pre-training needs

35)Test site/location

Outside test organizations to be utilized and their purpose, responsibilities,

deliverables, contact persons, and coordination issues

Relevant proprietary, classified, security, and licensing issues. Open issues