Flashcards
DEFECT LIFE CYCLE - Flash Cards
Cards in this deck (22)
- 1WHAT IS A DEFECT / BUG?⦁ When software is not working as per requirement
⦁ When something is preventing the software from working as per requirement
⦁ When something doesn't look right - 2WHAT IS A DEFECT / BUG? in simple termsthat threatens the value of the software to some person who matters
- 3SeverityImpact of the bug on the user's business. What effect will be there on a system due to the defect found
- 4Critical SeverityShow stopper
- 5Major SeverityIssue where the large piece of functionality is broken, but is not stopping us from testing further
- 6Minor SeverityIssue which doesn't have a big impact on user's operation or does not introduce a big threat
- 7What is defect Priority?Defect priority is defined by how soon the bug should be fixed
ex: High, Med, Low - 8USER IN PRODUCTION IS HAVING AN ISSUE Reporting system goes as follows: #1Client reports to > APS
- 9APS(APS - Application Production Support)
- 10USER IN PRODUCTION IS HAVING AN ISSUE Reporting system goes as follows: #2APS + Client = Troubleshoot
- 11USER IN PRODUCTION IS HAVING AN ISSUE Reporting system goes as follows: #3APS creates incident report > dev, qa, mgmt
- 12USER IN PRODUCTION IS HAVING AN ISSUE Reporting system goes as follows: #4qa try to reproduce in their env
WHILE dev work on a fix - 13USER IN PRODUCTION IS HAVING AN ISSUE Reporting system goes as follows: #5Once fix is given, the emergency release happens
- 14Did you find a defect? if no:DON'T OPEN A TICKET!
- 15Did you find a defect? if yes: step 1Open a new Jira ticket as bug or sub-bug
- 16Did you find a defect? if yes: step 2fill out necessary fields in Jira and the steps to reproduce the issue
- 17Did you find a defect? if yes: step 3assign to dev or dev mngr
- 18Did you find a defect? if yes: step 4 issue is valid? no:if no
resolve issue with resolution: "other"
and comment as "rejected" - 19Did you find a defect? if yes: step 4 issue is valid? yes:issue fixed by dev and code drop happened to qa env
- 20Did you find a defect? if yes: step 5 issue is valid? yes: retest Issue fixed: no (critical)if issue is not fixed the ticket will get re-opened from "dev complete" to "open" and goes back in the cycle
- 21Did you find a defect? if yes: step 5 issue is valid? yes: retest Issue fixed: no (NOT critical)defer issue to next sprint:
(change the fix version as per agreement with dev or product owner on when it will be fixed and mark ticket as "open" > issue goes back in cycle) - 22Did you find a defect? if yes: step 4 issue is valid? yes: retest Issue fixed: YESresolve the ticket as resolution "fixed"
Information
- Description
- QA Engineer QA- Fundamentals Flashcards on DEFECT LIFE CYCLE - Flash Cards, created by Mircea Manu on 03/12/2021.
- Created by
- Mircea Manu
- Views
- 0
- Rating