??“ Don??™t optimize yet.
This is another good reason for having threaded integration.
??? When system testing is almost finished and the code is reasonably stable.
7.4.5 What We Would Have to Do to Automate Our Tests
1.
Identify a suitable tool
.
2.
Design the tests
. Some things never change: tests need to be planned and specified as like anything
else. Most automated testing tools however provide facilities to let you specify tests long before
the test is scripted.
3.
Review the test designs.
You should still be able to use such designs for manual testing at a pinch.
Identify one test which is the highest possible priority because it represents the most probablyexercised
path through the system. List the other cases in order of priority. Check your priorities
with the developers, marketing, and any user representatives. The top-priority tests should be part
of the smoke, confidence, and regression test sets.
4.
Automate and run that test
such that it can be copied and modified to provide different use
scenarios.
5.
Automate and run the other tests
according to the (revised) priorities.
6.
Consider using a code profiling tool
to assess how much of the code is really exercised by the
automated test tool. This will have a delaying effect on the code which may give rise to spurious
timing problems.
7.
Document the tests
(minimally) such that:
a. Each function (
???open a file,??? ???close a file???
) has a simple and obvious name.
Pages:
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262