Error: It is a human mistake. We can say a mistake was made by the developer.
Bug/defect: It is the difference between the expected and actual results.
Failure: It comes in a customer/client environment. Where applications are unable to perform their functions.
Defects/Bugs/Issues:
Any mismatched functionality found in an application is called a Defect/Bug/Issue.
During Test Execution Test engineers are reporting mismatches as defects to developers through templates or using tools.
Defect Reporting Tools:
Clear Quest
DevTrack
Jira
Quality Center
Bug Zilla etc.
Defect life cycle is also called as bug life cycle. It has 6 stages namely.
New: found new bug
Assigned: bud assigned to developer
Open: developer is fixing the bug
Fixed: developer has fixed the bug
Retest: tester retests the application
Closed/ Re-opened: if it is ok tester gives closed status else, he re-opens and sends back todeveloper.
Defect Resolution:
After receiving the defect report from the testing team, the development team conducts a review meeting to fix defects. Then they send a Resolution Type to the testing team for further communication.
Resolution Types:
Accept
Reject
Duplicate
Enhancement
Need more information.
Not Reproducible
Fixed
As Designed.
Defect Severity:
Severity is assigned/given by the QA Testers.
It affects the functionality.
Severity describes the seriousness of the defect and how much impact on Business workflow (functionality). It is categorized into Blocker, Critical, Major, Minor.
Defect Priority
Priority is mostly given/assigned by the developer.
It affects business values.
Priority describes the importance of defects. The defect which is urgent for repair.
Defect Priority states the order in which a defect should be fixed.
Defect priority can be categorized into three categories:
P1: The defect must be resolved immediately as it affects the system severely and cannot be used until it is fixed.
P2: It can wait until a new version/build is created.
P3: The developer can fix it in later releases.
0 Comments