The important life cycle towrds the end of the project realease lets learn in detail
Terminologies
Error|Bug|Defect
Error is a terminology which is associated with the code so used by developers in white box testing.
Bug is a terminology which is associated with the functionality and user interface used by tester in black box testing.
Defect is a terminology which is associated with the end product used by end user in live.
Definition :Any unexpected and unwanted behaviour of the application can be called as a bug in tester prospective.
Reasons or sorces of bug:
Incorrect/Improper/Incomplete requirement.
Technology/Developer limitation to acheive 100% of the requirement.
Severity
Severity:Severity talks about the impact of the bug on the application
Severity levels:Actually there is no standard way of defining severity levels of the bugs still lets go with the following things
Critical:The instances where bugs are completely blocking your testing activities .The example instances are
system crash, massive performance degradation, data corruption, data loss, security violation
Major:The instances where major/important functionality failures.The example instances are operational error, data integrity, some performance degradation, loss of functionality (no workaround)
Minor:The minor functionality failures/Defect causes failure of non-critical aspects of the system.There is a reasonably satisfactory work around.
Trivial/Cosmetic:This is look and feel associated bugs ,there is no much concern about these things until unless its very primary requirement.
Priority:Priority is all about the prefernce in fixing the bugs
Priority levels:
Immidiate:
-Blocks further testing
- Currently very visible and/or deterimental to customers
- Possibly immediately detrimental to revenue or reputation
- Needed for time critical deadline
High:
- must fix before next release because of:
- numerous customer complaints about the issue
- critical area of the system
- will be very visible and/or deterimental when released
- does not conform to what was stated as a requirement for the release
Medium:
- should fix if time permits; not a critical areas of the system
- some customers are impacted by it but there is a workaround
- very few customer complaints logged about this issue
Low:
- would like to fix but can be released as is; trivial, cosmetic
- few customers even notice it much less are impacted by it
Buglife cycle flow diagram:
Bug Status:
1.New
2.Open
3.Fixed
4.Closed
5.Reopen
6.Duplicate
7.Deffered
Bug Report:
BUG REPORT FORM
YOURS COMPANY’S NAME CONFIDENTIAL PROBLEM REPORT
PROGRAM RELEASE VERSION
REPORT TYPE (1-6)___ SEVERITY ______________ ATTACHMENTS (Y/N)____
PROBLEM SUMMARY
CAN YOU REPRODUCE THE PROBLEM?(Y/N)___ STEPS TO REPRODUCE________________
PROBLEM AND HOW TO REPORT
SUGGESTED FIX (optional)
REPORTED BY DATE__/__/__
ITEMS BELOW ARE FOR USE ONLY BY THE DEVELOPMENT TEAM
FUNCTIONAL AREA ASSIGNED TO
COMMENTS
STATUS _____ PRIORITY (1_5)___
RESOLUTION (1-9)__ RESOLUTION VERSION
RESOLVED BY DATE__/__/__
RESOLUTION TESTED BY DATE__/__/__
TREAT AS DEFERRED (Y\N)
Terminologies
Error|Bug|Defect
Error is a terminology which is associated with the code so used by developers in white box testing.
Bug is a terminology which is associated with the functionality and user interface used by tester in black box testing.
Defect is a terminology which is associated with the end product used by end user in live.
Definition :Any unexpected and unwanted behaviour of the application can be called as a bug in tester prospective.
Reasons or sorces of bug:
Incorrect/Improper/Incomplete requirement.
Technology/Developer limitation to acheive 100% of the requirement.
Severity
Severity:Severity talks about the impact of the bug on the application
Severity levels:Actually there is no standard way of defining severity levels of the bugs still lets go with the following things
Critical:The instances where bugs are completely blocking your testing activities .The example instances are
system crash, massive performance degradation, data corruption, data loss, security violation
Major:The instances where major/important functionality failures.The example instances are operational error, data integrity, some performance degradation, loss of functionality (no workaround)
Minor:The minor functionality failures/Defect causes failure of non-critical aspects of the system.There is a reasonably satisfactory work around.
Trivial/Cosmetic:This is look and feel associated bugs ,there is no much concern about these things until unless its very primary requirement.
Priority:Priority is all about the prefernce in fixing the bugs
Priority levels:
Immidiate:
-Blocks further testing
- Currently very visible and/or deterimental to customers
- Possibly immediately detrimental to revenue or reputation
- Needed for time critical deadline
High:
- must fix before next release because of:
- numerous customer complaints about the issue
- critical area of the system
- will be very visible and/or deterimental when released
- does not conform to what was stated as a requirement for the release
Medium:
- should fix if time permits; not a critical areas of the system
- some customers are impacted by it but there is a workaround
- very few customer complaints logged about this issue
Low:
- would like to fix but can be released as is; trivial, cosmetic
- few customers even notice it much less are impacted by it
Buglife cycle flow diagram:
1.New
2.Open
3.Fixed
4.Closed
5.Reopen
6.Duplicate
7.Deffered
Bug Report:
BUG REPORT FORM
YOURS COMPANY’S NAME CONFIDENTIAL PROBLEM REPORT
PROGRAM RELEASE VERSION
REPORT TYPE (1-6)___ SEVERITY ______________ ATTACHMENTS (Y/N)____
PROBLEM SUMMARY
CAN YOU REPRODUCE THE PROBLEM?(Y/N)___ STEPS TO REPRODUCE________________
PROBLEM AND HOW TO REPORT
SUGGESTED FIX (optional)
REPORTED BY DATE__/__/__
ITEMS BELOW ARE FOR USE ONLY BY THE DEVELOPMENT TEAM
FUNCTIONAL AREA ASSIGNED TO
COMMENTS
STATUS _____ PRIORITY (1_5)___
RESOLUTION (1-9)__ RESOLUTION VERSION
RESOLVED BY DATE__/__/__
RESOLUTION TESTED BY DATE__/__/__
TREAT AS DEFERRED (Y\N)
No comments:
Post a Comment