• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
QA - Bug life cycle - An Overview
 

QA - Bug life cycle - An Overview

on

  • 248 views

 

Statistics

Views

Total Views
248
Views on SlideShare
248
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    QA - Bug life cycle - An Overview QA - Bug life cycle - An Overview Document 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.