As each bug is received it should be analyzed, and the test
which should have found it should be analyzed to see why it didn??™t and then modified or replaced.
??? Tests are analyzed and modified.
??? A new release is planned.
93
7
Testing Processes
and Infrastructure
This section covers the tools and documents you will need to manage and run your tests.
7.1 Initiation
7.1.1 Test Strategy
Use the test strategy document to hold and refine your overall views of the job, keep a sense of your
direction and priorities, and all the rarely-changing stuff. Review it every six months or when something
major happens to the project??™s objectives or environment. See section 8.3 and of course section 1.8.2 for
more details.
If at First You Don??™t Succeed,
Then Bungee Jumping??™s Not
for You
here is a company in Seattle. It makes, among other things, operating systems. One of
them is called DOS. It wanted to make a better one. It tried. It was quite proud of its
second attempt, and asked an Internationally Big Manufacturer to test it. For technical
reasons (in which the phrase ???
not with a bargepole
??? appeared) the testing was subcontracted to a
British software house. The results were predictable and unwelcome. Much blood was washed out
of Seattle carpets, and attempts numbers 3.0 and 3.11 were made.
Moral: whenever any manager tells you that what matters is time-to-market and not quality
(
???because that??™s how Microsoft does it???
), remember that that??™s what some people
say
Microsoft does.
Pages:
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250