Severity:It is the rating given to the bug based on how the bug is going to effect the functionality of the product/project we are building. How much deviation from the expected results and whether we can survive with the bug going forward or needs to get fixed before proceeding further.
Sev 1 Bug: This is bug is much like a stop stopper for the functionality and testing cannot be proceeded with this bug Active. This needs to be fixed for the testers to continue testing.
This is completely deviating from the expected functionality or would be leading to major issues in the product.
Example: System crashes when the user click on the Print button(major functionality of the product we are building) on a web page.
Sev 2 Bug: This the deviation from the functionality. Major functionality breakage but still we would be able to continue testing the other functionalities of the Project/Product.
Example: Not able to submit the input page. But still able to do validation checks on the page and for time being workaround exists for user to navigate to other pages.
We cannot sign off on the products if we have Sev 1 and Sev 2 projects in Open Status.
Sev 3 Bug: This is a slight deviation from the functionality and of not much importance to consider. These would be some UI functionalities, features that do not much effect the flow of project.
Project can be signed off even if they have Sev 3 bugs and which can later be taken known issue and can be considered to be fixed in next upcoming CR or a Bug fix drop.
Sev 4 Bug: These are the issues that could be a typo or product improvement suggestion. These consist of UI, Error messages/Validation checks etc.
Priority: This is the scale to define how to segregate the raised bugs to the concerned developer to fix the bug.And how much important the issue is to be fixed as early as possible.
When working on the bugs, priority helps the people to decide which work to take up first.
Priority 1: The bug needs to be fixed as soon as possible.
Priority 2: This bug needs to be taken care of to move to the next level.
Priority 3 and 4: The bugs can be handled later and some time can be taken as suggestion and can be implemented as a part of future releases.
Priority and Severity for a bug is defined and set in the bug triage meetings.And this helps in segregating the bugs and taking the most important ones into consideration and maximum utilization of time and resource for the project to be finished with in the time lines.
Priority and Severity could change based upon the project/project we are building.
Sev 1 Bug: This is bug is much like a stop stopper for the functionality and testing cannot be proceeded with this bug Active. This needs to be fixed for the testers to continue testing.
This is completely deviating from the expected functionality or would be leading to major issues in the product.
Example: System crashes when the user click on the Print button(major functionality of the product we are building) on a web page.
Sev 2 Bug: This the deviation from the functionality. Major functionality breakage but still we would be able to continue testing the other functionalities of the Project/Product.
Example: Not able to submit the input page. But still able to do validation checks on the page and for time being workaround exists for user to navigate to other pages.
We cannot sign off on the products if we have Sev 1 and Sev 2 projects in Open Status.
Sev 3 Bug: This is a slight deviation from the functionality and of not much importance to consider. These would be some UI functionalities, features that do not much effect the flow of project.
Project can be signed off even if they have Sev 3 bugs and which can later be taken known issue and can be considered to be fixed in next upcoming CR or a Bug fix drop.
Sev 4 Bug: These are the issues that could be a typo or product improvement suggestion. These consist of UI, Error messages/Validation checks etc.
Priority: This is the scale to define how to segregate the raised bugs to the concerned developer to fix the bug.And how much important the issue is to be fixed as early as possible.
When working on the bugs, priority helps the people to decide which work to take up first.
Priority 1: The bug needs to be fixed as soon as possible.
Priority 2: This bug needs to be taken care of to move to the next level.
Priority 3 and 4: The bugs can be handled later and some time can be taken as suggestion and can be implemented as a part of future releases.
Priority and Severity for a bug is defined and set in the bug triage meetings.And this helps in segregating the bugs and taking the most important ones into consideration and maximum utilization of time and resource for the project to be finished with in the time lines.
Priority and Severity could change based upon the project/project we are building.
No comments:
Post a Comment