Monitors the state of unit-tested bug fixes in the present
build
to ensure they are tested as early
as possible
c. Generates bug logs and bug charts
d. Lists the rarely-occurring, irreproducible, but potentially-dangerous problems
e. Looks for patterns of, and in bugs
f. Issues an updated bug metrics log
104 Manage Software Testing
This is a simple bug cycle and the one you evolve will probably differ. One probable cause of such a
difference is the use of the change request, whereby all bug reports authorized to be fixed have that
authorization embodied in a change request form, thus uniting the flow of information from bugs, with
that deriving from customer- or other-inspired changes. Other changes may derive from differing terms
used by the tool supplier.
7.6.1 Tracking Bug Reports
Testing is the prime means of providing objective information both about the quality of the software as
well as the process that produced it. To save time it is essential that all bugs and accompanying fixes, as
well as any enhancements, are tracked on a database. See Appendix D for details of some commerciallyavailable
ones.
7.6.2 Bug-Tracking Graphs
The bug reporting database should also be able to produce graphs showing:
??? The expected number of bugs found and their type
??? The actual number of bugs found and their type
??? The number of bugs fixed
??? The length of time some bug has been in the software
??? The number of outstanding bugs discovered over one month ago but not yet fixed
??? The cause of each bug.
Pages:
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270