BUG life cycle
As Soon After a Tester Identify The
Defect , It Will Be Recorded in a Bug Report Template Or Bug reporting Tool
with The Status New.
All New Defects Will Be Reported To
Developer , Now Developer Will Analyze Defect For
Conformation . If Reported Defect Is Invalid Then Developer Assign The Status
As Rejected . Rejected Defects Will Send Back To Tester . If Reported Defects is Valid
Conformation . If Reported Defect Is Invalid Then Developer Assign The Status
As Rejected . Rejected Defects Will Send Back To Tester . If Reported Defects is Valid
Then Developer Will Set The Status as
Open . If Defect Information Is Not Clear
Then Developer Assign The Status as Hold and Communicate To The Tester To get
More Info About Defect .If a Defect
is Postponed To Next Phase Then Developer Assign
The Status as Differed . If The Defect Is Already Reported Then Developer Assign The
Status
as Duplicate . Once The Defect Analysis Is Made Developer Starts Fixing Defects Based
The Status as Differed . If The Defect Is Already Reported Then Developer Assign The
Status
as Duplicate . Once The Defect Analysis Is Made Developer Starts Fixing Defects Based
On Defect Priority . Soon After a
Defect Is Fixed Developer Assign The Status as Resolved .
Once All Major Defects Are Fixed Then Modified Build Release To Tester For Re-Testing .
If The Defect
Is Properly Fixed In Modified Build Then Tester Specify Status As Closed , If not Properly Fixed Then Tester Will Re-Open
The Defect And Send Back To Developer . If A New Defect Is Identified In
Modified Build It Will Be Recorded with The Status New
And The Same Cycle Will Be Continued Once All Major Defects Are Fixed Then Modified Build Release To Tester For Re-Testing .
No comments:
Post a Comment