Prev | Current Page 89 | Next

Peter Farrell-Vinay

"Manage Software Testing"

He??™d just have
to get up there on stage and show them. So he did, and the play gelled and was a great success,
because he knew that play backwards. Indeed, he was well on his way to becoming an expert.
Moral: with the script in your head you can play it any way you want.
S
10
Manage Software Testing
All tests exist to answer some question.
Unit
,
integration
,
and system
tests
answer the questions ???
Do
the units do what they??™re supposed to? Do the components integrate properly? Does the system do what is
required of it???? To minimize risk, these questions are answered in phases: unit, integration, and system
testing. Since testing will certainly cost a third and perhaps more than half the total cost of the project,
planning and managing it is a major problem.
Tests get specified in test specifications (yes, some people call them test plans, but this is wrong). The
test specifications may in fact be inputs directly to some test tool. If not, they should contain at least the
essence of the test as shown in section 8.8.
1.8.4 Reviews
Testing is one of the main methods of demonstrating that the requirements of a project are met. Another
method is reviewing. This book is not concerned with how to review or how to manage a review, other
than test-readiness reviews. Look at [Freedman], [Wiegers], [Gilb], [Hollocker], and [Yourdon] in the
list of references at the back of the book for books on reviewing.


Pages:
77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101