Dupli

cate
Bug:
Alrea
dy a
bug
is
logge
d for
the
same
issue
Defer
red:
The
fix of
the
bug
is
postp
oned
to
some
future
relea
se.
Fixed
but
not
patch
ed:Th
e bug
is
resol
ved
but
the
fix is
yet to
push
ed to
testin
g
insta
nce.
Read
y for
retest
ing
:The
fix is
push
ed to
testin
g
insta
nce
and
ready
for
retest
ing
by
tester
Close
d,fix
verifi
ed: T
he
tester
verifi
es
the
fix
and
the
bug
is
resol
ved
comp
letely
Close
d,Not
a
bug: 
The
tester
verifi
es
the
bug
and
finds
the
bug
does
not
requi
re
code
fix
Close
d,Du
plicat
e
bug:
Reop
ened:
The
tester
verifi
es
and
finds
the
bug
is not
fixed(
either
comp
letely
or
partia
lly)
Lifec
ycle
of
som
e
type
s of
bug
s
Valid
bug: 
New
->
Assig
ned
->
Fixed
but
not
patch
ed ->
Read
y for
retest
ing ->
Clos
ed,fix
verifi
ed
Invali
d
bug: 
New
->
Not a
Bug
->
Clos
ed,N
ot a
bug
Dupli
cate
bug: 
New
->
Dupli
cate
Bug
->
Clos
ed,D
uplic
ate
bug
Reop
ened
bug: 
New
->
Assig
ned
->
Fixed
but
not
patch
ed ->
Read
y for
retest
ing ->
Reop
ened
->
Fixed
but
not
patch
ed ->
Read
y for
retest
ing ->
Close
d,fix
verifi
ed
Anal
ysis
of
bug
s
Bugs
logge
d
durin
ga
testin
g
phas
ea
inval
uable
sourc
e to
impro
ve
the
existi
ng
testin
g
proce
sses.
The
holyg
rail
for
any
testin
g
team
is
zero
custo
mer
bugs.
Once
a
produ
ct is
relea
sed,
major
ity of
the
custo
mer
bugs
come
within
6mon
ths to
1
year
of
produ
ct
usag
e.
But
imme
diatel
y
after
a
testin
g of
produ
ct is
over
the
follow
ing
can
be
done.
-
Testi
ng
Team
shoul
d
analy
ze all
the
invali
d/dup
licate
/coul
d_not
_be_r
eprod
uced
bugs
and
come
up
with
meas
ures
to
reduc
e
their
count
in
future
testin
g
effort
s.
Once
custo
mer
bugs
start
pouri
ng in
the
follow
ing
can
be
done.
-
Testi
ng
Team
shoul
d
analy
ze
each
and
every
custo
mer
bug,fi
nd
out
why
they
have
miss
ed
them
in
their
testin
g
effort
and
take
appro
priate
meas
ures.