has been a wonderful experience working towards this certification with
your training program, and I would give a very high recommendation to
any future users.
Newsletter Issue 58
Creating Relevant, Achievable Test Strategies
[This is an excerpt from my book, Expert Test
Manager, written with James Rommens and Leo van der Aalst. I hope
it helps you think more clearly about the test strategies you use.]
A test policy contains the mission and objectives of
testing along with metrics and goals associated with the
effectiveness, efficiency, and satisfaction with which we achieve
those objectives. In short, the policy defines why we test.
While it might also include some high-level description of the
fundamental test process, in general the test policy does not talk
about how we test.
The document that describes how we test is the
test strategy. In the test strategy, the test group explains how the
test policy will be implemented. This document should be a general
description that spans multiple projects. While the test strategy can
describe how testing is done for all projects, organizations might
choose to have separate documents for various types of projects. For
example, an organization might have a sequential lifecycle test
strategy, an Agile test strategy, and a maintenance test strategy.
Contents of the Test Strategy
Because the test strategy describes how testing
proceeds, independent of any particular project, the document can
include any information that is not project specific. (While we use
the word document, the test strategy could be a set of pages
on the company intranet or an internal wiki.) For example, the test
strategy may include material on the following topics:
specification techniques. This material should discuss
the process by which the test basis is analyzed and documented
and then decomposed into specific tests. In other words, how
does the test team gather information about the project and
product, generate a set of test conditions to be covered,
generate sufficient tests from those conditions, maintain
traceability, and assure the quality of those work products
(e.g., with reviews)? It can also include links to various templates
used for documenting tests, guidelines on the level of detail
required in tests, rules for documenting references to the test
basis and test oracle, and procedures for updating tests when
the test basis or test oracle change or a defect is detected in
and independence of testing. This material can
describe how to coordinate across the different levels of
testing, which are typically carried out by different
participants who have different degrees of independence. For
example, the test strategy may specify that unit testing is
performed by developers, integration testing by developers and
technical test analysts, system testing by business-oriented
test analysts and technical test analysts, and user acceptance
testing by senior users of the application being developed. It
may further specify how these different groups coordinate their
efforts to eliminate any gaps or overlap that might occur.
environments. This material should describe
the hardware, software, infrastructure, facilities, networking
capabilities, and other equipment needed for testing. To the
extent that the test environments differ from the production or
customer environments, the test strategy should describe the
impact of those differences on the testing results. If, for
unavoidable reasons, test environments must be shared across
test levels or production hardware used for testing, the test
strategy should describe how to coordinate that sharing and how
to manage the attendant risks.
This material should include information on how test data is to
be obtained, created, maintained, and managed during testing. If
production or actual customer data is to be used, the security
of sensitive information should be considered and procedures
around both access and use of such data should be put in place.
automation. This material should describe the use of
automation in the various test levels. In organizations where
extensive test automation is used-for example, to automate
functional regression tests or unit tests-this section could
consist of links to other documents that describe the tools to
be used, their acceptable usage, documentation requirements, and
To see the remaining contents of the test strategy and
to enjoy this article in its entirety today click
Copyright © 2017, RBCS, All Rights Reserved
RBCS' ISTQB Advanced Level Security Tester Course
Debuts with a 100% Pass Rate!
RBCS delivered its first live ISTQB Advanced Level
Security Tester course this month and yielded a 100% pass rate!
What are you waiting for? Sign up today!
one day conference
one-on-one with the guest presenters
your challenges with peers during the breaks and evening
The ASTQB volunteers and your fellow certified testers
are looking forward to seeing you and helping advance your career.
Analysis / UAT
you miss the complimentary webinar, "Enterprise Challenges
of Test Data" on May 16, 2017? Check out what you missed!
attendees are automatically entered into a drawing to win their
choice of one of our green e-learning
Sørensen , attendee of the May
webinar, for being selected as the winner of an e-learning
now for our
next complimentary webinar, "Stupid Metrics Tricks and How
to Avoid Them" on July 6, 2017.
all scheduled upcoming complimentary webinars and sign up today!
Do you follow us on Twitter or Facebook, or subscribe
to the RBCS YouTube channel? If you're on LinkedIn, are you
connected with Rex Black? Rex posts insights, free resources, and
links to interesting stuff in those spots pretty much every day.
Here's how to find us:
RBCS Software Testing Training Schedule
We are continuing to add to our 2017 schedule.
If you have a request for public training in your city and can
guarantee a minimum of 5 people in attendance, contact
us. We will be happy to schedule a course on your home
All RBCS courseware can also be delivered privately,
onsite, at your organization. Contact us
for pricing and to schedule.