??? All changes have been reviewed.
Agility
rather is
promoted
by
not
leaving hostages to fortune in the form of unforeseen change implications
and inconsistent documents. Real agility means changing direction faultlessly.
96
Manage Software Testing
7.2.3 Making and Testing Code Changes
The procedure for making and testing code changes involves the use of two libraries:
1. The personal library of the programmer making the change
1
2. The system-build library which holds unit-tested code ready for system testing and eventually
system-tested code for release and evolution
The procedure is as follows:
??? The programmer authorized to make the change obtains a copy of the unit(s), and unit test(s)
from the system library, and moves them to the programmer??™s personal library.
??? The changes are made to the code and unit tests as required, and are then unit tested in the
programmer??™s personal library.
??? The changed code and unit test results are reviewed by the Change Control Board and are either
rejected (in which case the programmer reworks the code to the Change Control Board??™s satisfaction)
or approved, in which case the code is incorporated in the build.
??? Any integration tests for the build incorporating the changes are updated and once the build is
successfully integration tested, the units are moved into the integration library. Bias the regressiontesting
parts of the integration tests particularly to exercise the changed units.
Pages:
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255