TEST PLAN

Test plan
• Detailed document that describes the test strategy,
objectives, schedule, estimation, deliverables, and
resources required to perform testing for a
software product.
• Helps us determine the effort needed to validate
the quality of the application under test.
• Serves as a blueprint to conduct software testing
activities as a defined process, which is minutely
monitored and controlled by the test manager.
How to write a Test Plan?
8 Steps:
1.Analyze the product
2.Design the Test Strategy
3.Define the Test Objectives
4.Define Test Criteria
5.Resource Planning
6.Plan Test Environment
7.Schedule & Estimation
8.Determine Test Deliverables
Scenario: E-commerce website

Step 1) Analyze the product

•Who will use the website?
•What is it used for?
•How will it work?
•What are software/ hardware the
product uses?
Step 2) Develop Test Strategy
Step 2.1) Define Scope of
Testing
• Before the start of any test activity, scope of the
testing should be known. You must think hard
about it.
• The components of the system to be tested
(hardware, software, middleware, etc.) are defined
as “in scope“
• The components of the system that will not be
tested also need to be clearly defined as being “out
of scope.”
The customer agrees and accordingly the new
scopes, out of scope items are
•In-scope items:
Functional Testing, API Testing
•Out of scope items
Database Testing, hardware & any other
external interfaces
Step 2.2) Identify Testing Type
 Step 2.3) Document Risk &
Issues
Risk Mitigation
Team member lack the required Plan training course to skill up your
skills for website testing. members
The project schedule is too tight;
Set Test Priority for each of the
it’s hard to complete this project
test activity.
on time
Test Manager has poor Plan leadership training for
management skill manager
A lack of cooperation negatively Encourage each team member in
affects your employees’ his task, and inspire them to
productivity greater efforts.
Establish the scope before
beginning work, pay a lot of
Wrong budget estimate and cost
attention to project planning and
overruns
constantly track and measure the
Step 2.4) Create Test Logistics

In Test Logistics, the Test Manager

should answer the following questions:
•Who will test?
Types of tester
•When will the test occur?
Step 3) Define Test Objective

Two steps:
•List all the software features (functionality,
performance, GUI…) which may need to test.
•Define the target or the goal of the test
based on above features
Step 4) Define Test Criteria

• a standard or rule on which a test procedure

or test judgment can be based
There are 2 types of test criteria as following
Suspension Criteria

Exit Criteria
Suspension criteria:

• Specify the critical suspension criteria for a test.

• If the suspension criteria are met during testing, the
active test cycle will be suspended until the criteria
are resolved.
Test Plan Example:
If your team members report that there are 40% of
test cases failed, you should suspend testing until
the development team fixes all the failed cases.
Exit Criteria

• Specifies the criteria that denote

a successful completion of a test phase.
• The exit criteria are the targeted results of
the test and are necessary before proceeding
to the next phase of development.
Example: 95% of all critical test cases must
pass.
• Run rate is ratio between number test cases executed/total
test cases of test specification.
For example, the test specification has total 120 TCs, but the
tester only executed 100 TCs, So the run rate is 100/120 =
0.83 (83%)
• Pass rate is ratio between numbers test cases passed / test
cases executed.
For example, in above 100 TCs executed, there’re 80 TCs that
passed, so the pass rate is 80/100 = 0.8 (80%)
• This data can be retrieved in Test Metric documents.
• Run rate is mandatory to be 100% unless a clear reason is
given.
• Pass rate is dependent on project scope, but achieving high
pass rate is a goal.
Step 5) Resource Planning

• Detailed summary of all types of resources required

to complete project task.
• Resource could be human, equipment and
materials needed to complete a project
• Important factor of the test planning because helps
in determining the number of resources (employee,
equipment…) to be used for the project.
• Test Manager can make the correct schedule &
estimation for the project.
Human Resource
No. Member Tasks
Manage the whole project
1. Test Manager Define project directions
Acquire appropriate resources

Identifying and describing appropriate test techniques/tools/automation

architecture
Verify and assess the Test Approach
Execute the tests, Log results, Report the defects.
2. Tester
Tester could be in-sourced or out-sourced members, base on the project
budget
For the task which required low skill, I recommend you
choose outsourced members to save project cost.

3. Developer in Test Implement the test cases, test program, test suite etc.

Builds up and ensures Test Environment and assets

4. Test Administrator are managed and maintained
SupportTester to use the test environment for test execution
Take in charge of quality assurance
5. SQA members Check to confirm whether the testing process is meeting specified
requirements
System Resource
No. Resources Descriptions
Install the web application under test
1. Server This includes a separate web server, database
server, and application server if applicable
The testing tool is to automate the testing,
simulate the user operation, generate the test
2. Test tool results
There are tons of test tools you can use for this
project such as Selenium, QTP…etc.
You need a Network include LAN and Internet
3. Network to simulate the real business and user
environment
The PC which users often use to connect the
4. Computer
web server
Step 6) Plan Test Environment
Step 7) Schedule & Estimation

Task Members Estimate effort

Create the test
Test Designer 170 man-hour
specification
Perform Test Tester, Test
80 man-hour
Execution Administrator
Test Report Tester 10 man-hour
Test Delivery 20 man-hour
Total 280 man-hour
To create the project schedule, the Test Manager needs
several types of input as below:
•Employee and project deadline: The working days, the
project deadline, resource availability are the factors which
affected to the schedule
•Project estimation: Base on the estimation, the Test
Manager knows how long it takes to complete the project. So
he can make the appropriate project schedule
•Project Risk : Understanding the risk helps Test Manager add
enough extra time to the project schedule to deal with the
risks
Gantt Charts
Step 8) Test Deliverables
Test deliverables are provided before testing phase.
•Test plans document.
•Test cases documents
•Test Design specifications.
Test deliverables are provided during the testing
•Test Scripts
•Simulators.
•Test Data
•Test Traceability Matrix
•Error logs and execution logs.
Test deliverables are provided after the testing
cycles is over
•Test Results/reports
•Defect Report
•Installation/ Test procedures guidelines
•Release notes