Specifications which match the level of testing we need to perform. Normally these are
Requirements
specifications,
which are the basis (or ???
baseline???
) of system tests;
Design specifications,
which are the basis of subsystem tests; and
Module specifications,
which are the basis of module
tests (Aka unit tests). As things get more complex you may use
HW/SW Interface specifications,
which are the basis of HW/SW interface tests;
KPIs (Key Performance Indicators)
,
which are
the basis of performance tests; and
User Interface specifications,
which are the basis of usability
tests. When web testing you may need to use user action logs and transaction flow maps. In
principle every kind of test has some baseline.
1
b.
What if the specifications don??™t exist, e.g., when testing games software?
There are times when
specifications that existed at the start are no longer useful. To expect programmers to define
what they??™re doing while they are in creative full flow would be like asking a centipede to think
Story: What the Bleep Was That?
nce upon a time a man invented an automatic garage door opener. It used a low-power,
short-wave transmitter operating on a little-used frequency, which the user kept in the
car. It sold very well, and the man made a lot of money.
Then Sputnik was launched. Guess what little-used frequency the Sputnik designers used.
And as Sputnik bleeped its way over America, garage doors opened and closed.
Pages:
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122