useful for testingstudents

1. Bug Life Cycle
Bug Life Cycle 1

2. PL or TL
defines the
status &
assigns to the
developer.
Bug Cycle
This indicates Status of the defect.
This indicates the task performed on defect.
This indicates the process done by tester or the developer on defects.
Bug Life Cycle 2
Both the team
will decide the
future of the
defect.
Bug reported
by a Tester
NEW
Invalid,
Rejected,
Deferred, Non
Re-creatable,
Duplicate
Assigned
Fixed
Verified & Fixed, Verified &
Not-Fixed, Closed
Developer
will fix it &
update the
defects
status.
Change the status
and reassign.
REOPEN
Tester will
verify it and
change the
status.

3. 1. New Bugs and enhancements are submitted in the Defect tracking system account
by the QA
2. Team Leader assigns priority to new Bugs and priority is updated in DTS.
3. R&D Team fixes bugs according to the priority assign, and changes the status to
‘Fixed’
4. R&D releases a new internal version, with fixed bugs and new features.
5. QA verifies and checked the bugs in new release, and changes the status
6. Fixed bugs are closed in the DTS by QA, Non fixed are ‘Reopened’ in DTS
Bug Life Cycle 3
New Bugs and
enhancements are
submitted in the
Defect tracking system
account by the QA
Team Leader assigns priority
to new Bugs and priority is
updated in DTS.
R&D Team fixes bugs according
to the priority assign, and changes
the status to ‘Fixed’
R&D releases a new
internal version, with
fixed bugs and new
features
QA verifies and checked the
bugs in new release, and
changes the status
Fixed bugs are closed in the
DTS by QA, Non fixed are
‘Reopened’ in DTS