qa - bug life cycle - an overview
Post on 20-Jan-2015
226 Views
Preview:
DESCRIPTION
TRANSCRIPT
Three conditions for something to be classified as a bug;
Retest the bug before filing to ensure that the bug is
1) Not a fluke 2) Not an error from QA side
Bug Tracking Tools = BugZilla and JIRA and QC
If the bug is rejected by the developer; Then try to read the docs and put your logic and explain to the developer. Then check the developer logic and if conflict still present then escalate the issue to the BA only if nothing works.
BUGZILLA DASHBOARD
Severity and Priority of Bug
Severity refers to the functionality; How much the code is broken. Priority refers to the business value of the bug and hence how soon the bug needs to be fixed. Hence, most of the times both are same. i.e S1 and P1 come together. Severity refers to the bug in cosmetic level or major recoverable functionality or unrecoverable
functionality or build failed. Priority refers to the business value that bug causes and hence how soon the bug needs to be
fixed.
top related