The scope of testing also covers the type of testing one needs to do like load testing, stress testing, for load and stress how many users test one is going to simulate. also what hardware it is going to use.
if requred one can also provide the schedule and what are elimiated in the testing, how many test cycle what is bug reporting and fixing work flow. etc.
Define and baseline build release plan to QA from dev. and so on Test plan should be what you are really addressing in the testing phase.
Login to rate this answer.
RTM as it is called is a important document which has trace from requirement to testing. The importance is that if during testing any bug is reported and thE developer needs to fix it and he makes certain changes to the code which leads to change in design then there should be a document which shows the dependencies clearly. RTM is used to trace requirements elements mapped to design elements which in turn are mapped to Code and their test cases. this gives complete coverage of the application.
Login to rate this answer.
Test plan is the one of the most important document that is required by testing team before actual testing begins. It is generally prepared by QA Manager/ Test Manager. This doc is prepared immediately after the requirement gathering phase is over. This doc includes various artifacts as:
Testing Strategy
Testing scope
Testing environment
Testing schedules
QA Deliverables
Out of scope testing
Resource allocation
Testing Task distribution
Contact points for various modules
etc....
1 User has rated as useful.
Login to rate this answer.
Has planning plays a very vital role in any thing we do... It goes the same with testing as well.... Test plan is the prime document which documents each and every thing pertaining to the testing of an application. Here are the contents of a good test plan...
Contents of test plan document:
1.Introduction
1.1 Objective
1.2 Reference documents
2.Coverage
2.1 Features to be tested
2.2 Features not to be tested
3.Test Statergy
3.1 Levels of testing
3.2 Types of testing
3.3 Test Design testing
3.4 Configuration Management
3.5 Test Matrics
3.6 Terminology
3.7 list of automated tools
3.8 Automation plan
4.Base Criteria
4.1 Acceptance criteria
4.2 Suspension criteria
5.Test Delivarables
6.Test Environment
7.Resource Planning
8.Scheduling
9.Staffing and training
10.Risks and Contingencies
11.Assumptions
12.Approval information
Regards,
Narin Kamuni
1 User has rated as useful.
Login to rate this answer.
Test Plan says how to schedule the testing along with different testing to be included with all deliverables. Basically it contains the scope of testing, what to test and what not to. Testing everything within a time period and fixed budget is not possible right. So defining the scope of testing along with testing methodologies which will meet client requirements.
Login to rate this answer.
This depends on the industry, company, and project. Generally my test plan includes:
1 INTRODUCTION
1.1 Purpose
1.2 Context
1.3 Target readership
1.4 Source material and references
2 OBJECTIVE AND SCOPE
2.1 System description
2.2 Test objectives
2.3 Scope of testing
2.3.1 Areas to be tested
2.3.2 Areas not to be tested
2.4 Stakeholders
2.5 Stakeholder preconditions
3 TEST STRATEGY DESCRIPTION
3.1 Overall approach
3.2 Risk Analysis
3.2.1 Test factors
3.2.2 Other factors
3.2.3 Contingencies
3.2.4 Recovery
3.3 Test phases
3.4 Stakeholder/Test phase matrix
3.5 Entrance criteria
3.6 Acceptance criteria
3.7 Exit criteria
4 TEST PLANNING
4.1 Major deliverables per test phase
4.2 Roles and responsiblities
4.3 Deliverables
4.3.1 Deliverables to test
4.3.2 Deliverables from test
4.3 Progress monitoring and reporting
4.4 Communication
4.5 Product delivery risk analysis
4.6 Assumptions and dependencies
5 TEST ORGANIZATION
6 TEST ENVIRONMENT AND TOOLS
7 TESTING STANDARDS AND CONVENTIONS
7.1 Configuration management and change control
7.2 Metrics
7.3 Test data
Login to rate this answer.
