8.8.3 Test Objective
Specify the purpose of the test, perhaps expressed in terms of an attempt to disprove some assertions in
some specification.
8.8.4 Baseline Definition
Define the baseline from which the objective was derived. This will usually be:
??? The requirements specification (for system tests)
??? The design specification (for integration tests)
??? The unit specification (for unit tests)
??? The user guide (for user interface tests)
??? The operations guide (for background advice)
??? The installation guide (for background advice)
This will enable you to relate the tests to the baselines and check that no baseline remains uncovered.
This should also relate the test to a feature so that the number of tests per feature can be determined.
8.8.5 Input Specifications
Specify:
??? Each input type required to execute the test case; some will be specified by value (with tolerances)
while others, such as constant tables or transaction files, will be specified by name.
??? Any special relations between the inputs for example with respect to order or timing, expressed
in the form of a grammar, state table, or Finite State Machine.
??? All data bases, files, terminal messages, memory-resident areas, and values passed by the operating
system.
??? All required relationships between inputs (for example, timing).
??? Where the input should be supplied by the operator and is not described in the test procedures
specification, specify:
??“ The mode or state the system should be in before the test, including the screen display.
Pages:
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333