Prev | Current Page 221 | Next

Peter Farrell-Vinay

"Manage Software Testing"

When you are in
the throes of test planning, use this as a way of abstracting out strategic issues.
??? Then draft a skeleton
test plan
showing all the testing activities of the project, preferably as a
separate document or as part of a draft quality plan (see section 8.21). This should indicate the
objectives, management, and processes of all the testing activities of the project as well as any risks
and commitments which justify them. Orient the test plan to the testing deliverables and establish
who is responsible for each deliverable and its testing. Get some sense of timing in place with a
Gantt or PERT chart (Figure 6.2). Check the test plan against the project plan and ensure that
the dates match and the stakeholders agree.
FIGURE 6.1
A test process
Start
Requirement
speci?¬?cations
Test
speci?¬?cations
No
Test
speci?¬?cations
Test estimates
Draft test plan
Revised tests
plan
Tests
Test results
Test reports
Problem
reports
Test strategy
document
Test
environment
details
Plan testing
Read speci?¬?cations
Estimate tests
Write test speci?¬?cations
De?¬?ne test environment
Write/automate tests
Run tests
Analyze results
Triage test results
Report tests
Modify tests
Release criteria
met?
Stop
Yes
The Overall Test Life-Cycle
85
The test plan can follow the IEEE model [IEEE 1012] mentioned in section E.2 in Appendix E.
However this could usefully be augmented with two extra sections covering reliability profiling
and risk.


Pages:
209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233