Do not attempt this with untested
software and untested hardware if you value your schedule.
Wherever possible, software should first be tested with hardware emulation software such as an In-
Circuit Emulator (ICE) and hardware should be tested with hardware test programs. Any such support
software and hardware should be suitably validated before use and maintained under configuration
control.
Any software embedded in a piece of hardware should be tested as a separate system first with a full
system test. Then their interfaces should be tested by placing each subsystem in an emulator. Once system
tests have been conducted on all such subsystems they can be amalgamated, and an overall end-to-end
system test conducted.
The Overall Test Life-Cycle
89
6.6 Test Readiness Review
The purpose of a test readiness review is to determine:
??? How ready the test team is to undertake system (and later) testing (
Have tests been written to cover
every requirement? Is the system sufficiently-documented?
)
??? To what extent the tests already executed demonstrate the system??™s readiness for release
??? To what extent the system??™s unit and other tests already undertaken indicate the system??™s readiness
for system testing
??? How representative the data proposed to be used during system testing is
Inputs to the review are:
??? The baseline documents, test plans, test objectives, and tests (which may include automated tests)
??? Results of pre-system test activities such as early test runs which demonstrate that the tests are
capable of finding problems
??? Results of installation and smoke tests
The review will (minimally) use section B.
Pages:
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242