Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
12 Cards in this Set
- Front
- Back
|
New |
New defect is logged and posted for the first time |
|
|
Open |
The developer starts analyzing and works on defect fix fixed |
|
|
Fixed |
When a developer makes a necessary code change and verified the change , the status goes to fixed |
|
|
Pending retest |
Once defect is fixed, the developer gives a particular code for retesting to the tester. It’s assigned as pending retest. |
|
|
Retest |
The stage that the tester is retesting the code that has been fixed after a defect |
|
|
Verified |
Retests the code and if no error is found, it is assigned as verified |
|
|
Reopen |
The bug persists even after the developer had fixed it, tester changes it to reopen |
|
|
Closed |
Closed if the bug no longer exists then status is closed |
|
|
Duplicate |
If the defect is repeated twice or corresponds to the same concept of the bug status is duplicate |
|
|
Rejected |
If the developer feels the defect is not a genuine defect, then it changes to rejected |
|
|
Deferred |
If the present bug is not a priority and it’s expected to get fixed in next release, status is deferred |
|
|
Not a bug |
If it does not affect the functionality of the application |
