QUALITY CENTER: DEFECT REPORTING GUIDELINES

When to Report a Defect:

The information provided guidelines when to report a test step as failed and how to distinguish test plan
defects from application defects:
When to report a test step as fa!e":
Report a defect if there is a difference between the expected result and the actual result, unless the defect
has already been reported.
#o$ to "stn%&sh test p!an "efects fro' app!caton "efects:
If the application clearly is correct (e.g. there is a typo in the test plan or the test plan is missing a navigation
step):
a( Pass the test step(
b. If the test plan is incorrect or needs clarification, document the test plan update by logging a defect
where:
tatus ! Test "lan
#ssigned to ! $your pro%ect&s test planner '
If the application clearly is not correct (e.g. you(ve received a system error):
a( Fa! the test step
b. )omplete the #ctual Result text field on the test step
c. *ocument the application error by logging a defect where :
tatus ! *raft
#ssigned to ! $your pro%ect&s defect manager'
d. If the test plan is incorrect or needs clarification, document the test plan update by logging a separate
defect where
tatus ! Test "lan and
#ssigned to ! $your pro%ect&s test planner '
+or all other defects,
a( Fa! the test step
b. )omplete the #ctual Result text field on the test step
c. *ocument the discrepancy by logging a defect where
tatus ! *raft
#ssigned to ! $your pro%ect&s defect manager'
QUALITY CENTER: DEFECT TRAC)ING PROCESS
,hen reporting defects, include as much detailed information as possible so the defect is easily understood
by others who may be wor-ing on the pro%ect.
S&''ar*:
creen name and short description about the defect being reported, usually providing
-ey words with which to identify and.or search for the defect.
Detecte" +*: #uto populates with the /ser I* of person logged in.
Detecte" on Date: #uto populates with current date.
0 1223 4 1225 Regents of the /niversity of 6innesota. #ll rights reserved. "age 7
Se,ert*: *escribes the degree of impact that a defect has on the operation of the application.
Ass%ne" To: Individual being assigned the defect for fixing.
Detecte" n +&!":
8uild I* in which the defect was found. 8uild I* is an identifier for the code release,
assigned by ,eb *evelopment.
F-e" n +&!":
8uild I* in which the defect is fixed. 8uild I* is an identifier for the code release,
assigned by ,eb *evelopment.
Prort*:
This field describes the impact the defect has on the wor- in progress and the
importance and order in which a bug should be fixed.
Stat&s: Indicates the existing state of a defect, auto populates with a default of 9:ew;
Descrpton:
<nter description of defect
#dd individual steps to reproduce. Include all steps and screens that were accessed.
<nter exact words of the error message.
E'a! Defect: #fter entering defect, right4clic- on it and select email to send to assigned developer.
Defect reso!&ton
process:
,hen the developer begins wor-ing on the defect, s.he changes status to 9#ssigned;.
=nce the defect is fixed:
7. The developer to whom the defect is assigned will update the defect
comments to document the fix that was made. /ser I* and *ate is
automatically added to the defect by clic-ing on 9#dd )omment;.
1. The developer to whom the defect is assigned will change the status to
9+ixed;, and will change the 9#ssigned To; field to the tester or defect
manager.
>. The tester will retest the submitted defect.
?. If defect passes the retest, the tester or defect manager will change tatus to
9@erified;.
A. If the defect is not fixed, the tester will change the tatus to 9Reopen; and
enter the /serI* of the developer in the #ssigned To field.
B. =nce the defect has been 9@erified;, the pro%ect manager (or defect manager)
will update the status to 9)losed;.
DEFINITIONS FOR DEFECT PRIORITY AND SE.ERITY
PRIORITY: This field describes the impact the defect has on the wor- in progress and the importance and
order in which a bug should be fixed. This field is utiliCed by the developers and test engineers to prioritiCe
wor- effort on the defect resolution.
/ 0 Ur%ent +!oc1s Wor1
+urther development and.or testing cannot occur until the defect has been
resolved.
2 0 Reso!,e ASAP
The defect must be resolved as soon as possible because it is impairing
development and.or testing activities.
3 0 Nor'a! Q&e&e
The defect should be resolved in the normal prioritiCation and completion of
defect resolution.
0 1223 4 1225 Regents of the /niversity of 6innesota. #ll rights reserved. "age 1
4 0 Lo$ Prort*
The defect is an annoyance and should be resolved, but it can wait until after
more serious defects have been fixed.
5 0 Tr,a! The defect has little or no impact to development and.or testing wor-.
SE.ERITY: This field describes the degree of impact that a defect has on the operation of the application.
/ 0 Crtca!
)ritical loss of function. The defect results in system crashes, the failure of a
-ey subsystem or module, a corruption or loss of data, or a severe memory
lea-.
2 0 6a7or
6a%or loss of function. The defect results in a failure of the system, subsystem,
or module, but the defect does not result in the corruption or loss of significant
data.
3 0 6o"erate
6oderate loss of function. The defect does not result in a failure of the system,
subsystem, or module, but the defect may cause the system to display data
incorrectly, incompletely, or inconsistently.
4 0 6nor
6inor loss of function, or another problem where a wor-around is present.
There are no data integrity issues.
5 0 Usa8!t*
The defect is related to the system usability, is the result of non4conformance to
a standard, or is related to the aesthetics of the system. There is no loss of
system function.
9 0 Enhance'ent
The defect is a reDuest for an enhancement, i.e. it is not within the scope of the
current pro%ect effort.
0 1223 4 1225 Regents of the /niversity of 6innesota. #ll rights reserved. "age >