Test Plans
White paper prepared by Codel
Services Ltd
©
Problem
A common
pitfall of testing activity is that it doesn’t test the right
functionality, or it spends too much time in some areas, or is too
detailed. These are the symptoms of poor planning, and can be mitigated by
the production of a test plan.
Solution
Before any
testing can commence, it is first important to understand the scope of:
 |
What is being tested:
Understand functionality, interfaces and architecture in and out of
scope |
|
How it is to be
tested:
Understand the range of test styles (boundary, non-functional, user
experience) that is necessary |
|
What are the
constraints:
Understand time and resource that are available for testing |
|
What is the fall-back:
What are the consequences of undetermined bugs? Not every application is
life-critical, and often defects can be managed as part of an iterative
cycle of development. |
Depending
on the answers to the above a completely different style of testing may be
appropriate.
Benefits
Codel Services has put together a test planning template that is designed
to suitable for most projects, and ensures that the right questions are
asked at the right time.
Ó
2002-2007 Codel Services Ltd
This paper has been prepared by Codel
Services Ltd to illustrate how structured business modelling can help
your organisation. Codel Services Ltd is an IT Consultancy specialising in
business modelling. If you would like further information, please contact
us at: Deryck Brailsford, Codel Services Ltd, Dale Hill Cottage, Kirby-Le-Soken,
Essex CO13 0EN,United Kingdom. Telephone: +44 (0)1255 862354/Mobile: + 44
(0)7710 435227/e-mail: info@codel-services.com
