Developing a Test Strategy

Overview

Testing Steps
Looking at UAT from a high level, there are a few basic steps that need to be
undertaken:

Step	Description
Test Strategy	Decide how we are going to approach the testing in terms of people, tools, procedures and support
Test Scenarios	What are the situations we want to test
Test Scripts	What are the actual inputs we will use? What are the expected results?

Test Strategy
Why do a Test Strategy? The Test Strategy is the plan for how you are going to approach testing. It is like a project charter that tells the world how you are going to approach the project. You may have it all in your head, and if you are the only person doing the work it might be OK. If however you do not have it all in your head, or if others will be involved, you need to map out the ground rules. Here are some of the things that need to be covered in a Test Strategy. You could use this as a template for your own strategy.

Project Name

Overview
Testing stage Instructions:
Identify the type of testing to be undertaken.
Example:
User Acceptance Testing
Scheduled for Example:
01.04.06 to 15.04.06
Location Example:
Testing will be carried out in the Test Center on Level X
Participants Instructions:
Identify who will be involved in the testing. If resources have not been
nominated, outline the skills required.
Example:
Testing Manager - J. Smith
2 Testers - To be nominated. The skills required are:
• Broad understanding of all the processes carried out by the accounts
receivable area.
• Should be familiar with manual processes currently undertaken for
reversing payments.
• Preferably spent time dealing with inquiries from customers over the phone
• Etc.

we plan to cover the product so as to develop an adequate assessment of quality.

A good test strategy is:

Specific
Practical
Justified

The purpose of a test strategy is to clarify the major tasks and challenges of the test project.

Test Approach and Test Architecture are other terms commonly used to describe what I’m calling test strategy.

Example of a poorly stated (and probably poorly conceived) test strategy:

“We will use black box testing, cause-effect graphing, boundary testing, and white box testing to test this product against its specification.”

Test Strategy: Type of Project, Type of Software, when Testing will occur, Critical Success factors, Tradeoffs

Test Plan - Why

· Identify Risks and Assumptions up front to reduce surprises later.

· Communicate objectives to all team members.

· Foundation for Test Spec, Test Cases, and ultimately the Bugs we find.

Failing to plan = planning to fail.

Test Plan - What

· Derived from Test Approach, Requirements, Project Plan, Functional Spec., and Design Spec.

· Details out project-specific Test Approach.

· Lists general (high level) Test Case areas.

· Include testing Risk Assessment.

· Include preliminary Test Schedule

· Lists Resource requirements.