What is a Test
Need a test plan for an
information management project and want practical suggestions to ensure
rapid project delivery?
A plan is a communications tool, which clearly sets testing expectations for all team members.
of it as a mini-project
documents test objectives,
roles and responsibilities, test deliverables, test tasks, defect
reporting requirements, entrance
criteria, that should be met before
formal testing commences; and the exit
criteria that must be met before
testing can be considered complete.
It helps new team members quickly see who is involved with the testing
and helps minimize project delays due to miscommunication.
Why is it
Suppose you have just had a new house built. Everything looks good to
you and you move in. Come winter, your water freezes, your
service short-circuits when you turn on the Christmas tree lights and
try to cook the turkey at the same time, and snow blows thru cracks in
the window frames.
This probably will never occur because we have building codes,
regulations and inspections to
construction meets standard.
information management standards?
The information management framework established project deliverable
practices. The quality
assurance plan ensures
development meets standards.
know everything works? We need to validate that the solution matches
specification and meets
requirements. This is where a good test
included in a test plan?
A test plan should include the following:
objectives, should summarize project objectives, test
scope and roles and responsibilities;
should refer to the requirements acceptance criteria,
that were developed as part of the requirements definition phase, and
environments that will be used;
should list the scope
of each test, including entrance
criteria, how test cases will be prepared, what test data will be used,
what test scripts are required, who will execute test
defects will be managed, how test results will be managed, and test
strategy, should list the overall approach for creating
data. Try not to use large
volumes of data for unit, system, integration,
regression and quality assurance testing.
complete these tests with a sub-set of data. Failure to do
this will add
significantly to the test period and will not
time it takes to create a complete set of test data
the project will be paid
many times by reducing the time to
back-up/restore data during testing;
deliverables should specify what will be produced;
should list all project roles and responsibilities, level
of effort, and other test resource requirements;
considerations, should list any training that might be
required so the test team can complete testing; and
should identify a test schedule that clearly defines
when all testing is expected to occur—This schedule may be included in
the project schedule.
types of testing are included in a test plan?
should focus on
testing individual modules to ensure that they perform to
specification, handle all exceptions as expected, and produce the
appropriate alerts to satisfy error handling;
testing should focus on testing a set of
components to ensure
that it performs to specification;
should focus on testing a set of components to ensure
that they meets requirements; and
management technical testing is required?
acceptance testing (UAT) should focus on testing a set of
requirements to ensure that they meet user expectations.
volume tests to confirm that the system is
operating correctly and can handle the required data volumes;
tests to manually confirm the validity of data;
- Regression testing
to ensure that the new software does not cause
problems with existing software;
- Performance testing to
ensure that data can be loaded in the
manager testing; and
- Infrastructure and
A test plan is a communications tool, which clearly sets testing
expectations for all team members. It is important to complete the plan
early in the project and manage it carefully to
ensure on time, within budget project delivery.
It is also important to recognize that the technical team
should perform much of the technical