The content of a test plan varies widely between industry, company and project. Nevertheless, I often include the following:
1) Introduction - Purpose - Product description - System architecture 2) Scope - Test coverage - Features to be tested (in scope) - Features not to be tested (out of scope) - Compatibility matrix - Assumptions - Risks 3) Approach - Test objectives - Test strategies - Test environment - System dependencies - Test tools 4) Process - Test process and guidelines - Priority and Severity definitions - Pass/fail criteria - Test entry/exit criteria - Test resources - Deliverables required for testing - Roles and responsibilities - Approvals and sign off
Showing Answers 1 - 17 of 17 Answers
Sanjay guha
May 25th, 2005
In brief a test plan should have the following sections in which the Methodology section will cover the test coverage Matrix with the approximate amount time expected to finish the test cases covered in this test plan. 1.Purpose 2.Scope 3. Methodology 4.Risks and Contingencies 5. References 6 Appendices
san
May 25th, 2005
Test Strategy, features to be tested, features not to be tested, hardware, software, risk and contingency, test deliverables, schedules, test environment, reference and approval.
Amith
Jun 19th, 2005
Test plan is used to plan the testing process,to carry out testing with a process oriented approach and the testing process effectively.It decides the resources required ,types of tools to be used,types of tests to be conducted.An acceptance plan is derived from a test plan.
choudary
Jul 4th, 2005
test plan is a plan which is used for testing process. in this document we determine the 1.test strategy. 2. the scope of the testing. 3. features to be tested and not to be tested. 4. resources required. 5. types of automation tools. 6. Risks 7. time estimation
Srinivas B.Joshi
Jul 13th, 2005
The test plan prescribe the approach to be taken for intended test activities, identifying: 1) the items to be tested, 2) the testing to be performed, 3) test schedules, 4) resource and facility requirements, 5) reporting requirements, 6) evaluation criteria, 7) risks requiring contingency measures.
Madan
Jul 21st, 2005
Title of Project? Author Name,Version ..Date of preparation? 1)Introduction? 2)objective? 3)Intended Audiences? 4)Acronyms? 5)Test Process? 6)Kinds of testing? 7)Test approach? 8)Functions to be Tested? 9)Functions not to be Tested? 10)Pass/Fail criteria? 11)suspension/Resumption Criteria? 12)Test Environments? 13)Test Deliverable? 14)Priorities AND Severity? 15)Responsibilities? 16) Entry/Exit criteria? 17)Release Notes
jobine
Jul 29th, 2005
whats the realtion between QA and a tester
kalpana naidu
Jul 29th, 2005
Test plan is a document that describes objective,scope,approach and focus of a software testing effort. usually test plan consists of: 1. History 2. Introduction 3. Features to be tested 4. Features not be tested 5. Time schedule 6. Resources 7. Test deliverables 8. Approvals etc.
chittaranjanrout
Aug 5th, 2005
Test Plan Contains the following. 1 - a .what to test. b. what not to test. 2. how to test. 3. who will test. 4.when to test(time schedule). 5.h/w, s/w requirements. 6.Risk and contingencies 7.Approvals.
Prasanna
Aug 5th, 2005
Test Plan is a big document that contains all the information about your project, objectives, scopes, roles and responsibilities, test-set(set of test cases), test -bed(types of testing, execution environment), test-strategy, schedules etc.
Valavan.S.R
Sep 14th, 2005
Test plan includes...
Test Plan identifier, Project Scope,Objectives, Feature to be and not to be tested, Test Setup, Test Approach/Strategy,Pass/ Fail criteria, Entry / Exit Critria,Time taken to test,Test deliverables, Risks, Training needs and resource needs ( H/W , S/W , Manpower, Cost), Reference doc details and Approvals.
Feroz Khan
Jul 5th, 2006
Hi friends ,
The Test Plan Design document helps in test execution it contain
Test Planning Activities 1. To determine scope and risks. 2. To define test strategies. 3. To integrate and coordinate test activities into SLC(software life cycle) 4. To make decisions on what to test and how results will be evaluated 5. To schedule test analysis and design. 6. To schedule test implementation and execution 7. To select metrics to monitor and control test preparation & defect resolution
*Metrics helps assess progress against planned schedule & budget
A test plan should include the following depending on the particular project.
Title of the project Tracebility requirments Location/site of testing relevant naming conventions and identifier conventions. purpose of documents. objective of testing effort relevant related document list such as requirments, design documents, other test plans overall software project organization and personnel/contact-info responsibilities table of contents
The test plan document contains
1. Test objective
2. Test goal
3. Roles and responsibilities
4. Communication approach
5. Risk analysis
Aftr that we have test case design, test execution, test log preparation, defect tracking, report writing.
In case case design, we have test case id, test case name, test data, test action, expected result, actual result, test status.
In defect tracking we have defect id, defect description, test case id, seviority, priority
These are basic, but it may differ frm company to company
The content of a test plan varies widely between industry, company and project. Nevertheless, I often include the following:
1) Introduction - Purpose - Product description - System architecture 2) Scope - Test coverage - Features to be tested (in scope) - Features not to be tested (out of scope) - Compatibility matrix - Assumptions - Risks 3) Approach - Test objectives - Test strategies - Test environment - System dependencies - Test tools 4) Process - Test process and guidelines - Priority and Severity definitions - Pass/fail criteria - Test entry/exit criteria - Test resources - Deliverables required for testing - Roles and responsibilities - Approvals and sign off
A Plan enables you in advance to decide up on 1. How the objectives can be met 2. With the resources available 3. With the Time scale required. 4. To the Quality desired 5. While controlling the risks.
A Test Plan can be categorized into 6 clauses. 1. Scope (Includes Test Items, Features to be tested, Features not to be tested). 2. Resources(Includes Environmental Needs, Responsibilities and Staffing and Training Needs). 3. Time (Includes Testing Tasks, Schedules) 4. Quality (Includes Introduction, Approach, Items Pass/Fail criteria and Test Deliverables) 5. Risks (Include Suspension criteria/Resumption requirements and Risk Mitigation and Contingency Plan). 6. Plan Clauses (Include Test Plan Identifier and Approvals).
What do you include in a test plan?
Editorial / Best Answer
kurtz182The content of a test plan varies widely between industry, company and project. Nevertheless, I often include the following:
1) Introduction
- Purpose
- Product description
- System architecture
2) Scope
- Test coverage
- Features to be tested (in scope)
- Features not to be tested (out of scope)
- Compatibility matrix
- Assumptions
- Risks
3) Approach
- Test objectives
- Test strategies
- Test environment
- System dependencies
- Test tools
4) Process
- Test process and guidelines
- Priority and Severity definitions
- Pass/fail criteria
- Test entry/exit criteria
- Test resources
- Deliverables required for testing
- Roles and responsibilities
- Approvals and sign off
Related Answered Questions
Related Open Questions