Académique Documents
Professionnel Documents
Culture Documents
http://www.mobilefish.com/tutorials/webdevelopment/webdevelopment_quickguide_bugtrac
king.html
Information
For large projects it is recommended to use a more advanced bug tracking tool such as
Bugzilla. For very small projects you can use this simple bug tracking system based on an
Excel spreadsheet.
Operating system used
Windows XP Home Edition Version 5.1 SP 2
Software prerequisites
Microsoft Excel
Microsoft Word
Procedure
1. The bug life workflow is as follow (click on image to enlarge):
First create a subfolder with the bug id as its folder name, for example:
C:\myproject\15
Copy the C:\myproject\bug_report_template.doc into C:\myproject\15
Rename the document into bug_report_15.doc
Place all additional information regarding this bug such as screen dumps and
log files in C:\myproject\15
Edit bug_report_15.doc
Column
Value
Description
Bug#
Originator -
Submit
date
Summary
Severity
1.6.blocker
Indicates how damaging the bug is and is set
by the bug reporter.
2.7.critical
3.8.major
4.9.minor
7.12.
Blocks development and/or
5.10.
trivial
testing work.
6.11.
enhance
8.13.
Crashes, loss of data, severe
ment
memory leak, performance problem.
9.14.
Major loss of function.
10.15.
Minor loss of function, or other
problem where easy workaround is
present.
11.16.
Cosmetic problem like
misspelled words or misaligned text.
12.17.
Request for enhancement.
Product
Component
Version
Platform
13.18.
14.19.
h
PC
The platform used when this bug is found.
Macintos
OS
15.20.
s
16.21.
17.22.
Browser
18.23.
19.24.
1.5
found.
Mac
Linux
IE 6.0
Firefox
URL
Description
Value
Description
Bug#
Originator -
Submit
date
Summary -
Severity
20.0.
21.1.
22.2.
23.3.
24.4.
25.5.
ment
Priority
32.12.
33.13.
34.14.
35.15.
36.16.
P1
P2
P3
P4
P5
Assigned
to
Resolution
critical
high
medium
low
unkown
fixed
Indicates what happened to the bug and is set by
invalid the developer.
wontfix
cantfix
49.29.
A fix for this bug is made.
needinfo
50.30.
The problem described is not a
Status
47.27.
48.28.
me
duplicate
worksfor
56.36.
57.37.
58.38.
59.39.
60.40.
61.41.
new
Indicates the general health of a bug.
assigned
resolved
62.42.
Bugs that are first opened and
verified
has not been assigned to anybody yet.
reopend
This status is set by the bug reporter.
closed
63.43.
The bug has been assigned to a
developer who will take charge of it.
This status is set by the lead developer.
64.44.
A fix for the bug has been
implemented and it is awaiting
verification by QA (Quality Assurance).
This status is set by the developer.
65.45.
The QA has verified the validity
of the bug fix. This status is set by the
QA.
The QA is usually a (lead) developer
verifying the bug fix and also reviews
the code if it complies to coding,
security and other standands.
66.46.
The bug was previously
resolved, verified or closed but it has
been reopened. This status is set by the
QA or tester.
67.47.
The tester verified the bug fix.
This status is set by the tester.