Backwards compatibility
RFCs
US Regionalization
Smoke and con?¬?dence
Schedules
Critical codes
Data sources
Password security
National language services
Miscellaneous
Long directories
Importing items
Hyperlinks
Minor transactions
0
Steps passed Steps N/A Steps not run Steps failed
200 400 600 800 1000 1200
0.105
Drop 6 test execution status as at 9-Sep-04 at 09:00
67
83
0 177
01
03
02
0 250
0
54
0111
05
0 77 901
90
441
01 235
125 35
146 Manage Software Testing
Figure 8.24 shows the same data as in the last chart but as a proportion. Release 13 is still being
tested. Note that the right-most (Medium and Low) bars remain largely static as the releases
progress (bad). A large number of critical and high bug reports is still being raised.
5. Feature stability profile. Some features are more stable than others. The less-stable are particular
candidates for regression-testing. Monitor them by ensuring that the bug-reporting tool can report
by feature and maintaining a chart like the one shown in Figure 8.25.
This shows the tendency of some features to instability. If the code for those features is also unstable
there is a very high probability that bugs are being created as fast as they are being fixed. Look in
the source code management system for the degree of code turmoil (see Chapter 18) as a check.
8.6.8 The Overall Tale
The charts tell a tale of a project which appeared stable until one looked closer.
Pages:
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328