Archives
- Newer posts
- April 2024
- November 2023
- October 2023
- August 2023
- May 2023
- February 2023
- October 2022
- August 2022
- July 2022
- May 2022
- April 2022
- March 2022
- February 2022
- June 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- August 2016
- June 2016
- April 2016
- March 2016
- February 2016
- January 2016
- July 2015
- June 2015
- Older posts
How big is a bug??
Software testing is all about finding bugs, isn’t it?
We all know that there is always a never ending battle between the developers and the testers. Developers think “How we can make the software” while the testers think “How can we break the software”. Combined efforts of both – the developers and testers – help us build and deliver high quality software to the customers.
An application with too many bugs is called “BUGGY”. Every application, big or small has bugs. It is not sufficient to only find bugs. We cannot deliver a good product to our clients just by finding bugs and never fixing them. Therefore, all the reported bugs need to be fixed and since each bug is different from the other, the order to fix the bug also differs.
Severity and Priority are the two terms used to decide which bug gets fixed and in which order. Severity is the degree of impact the bug has on the system. On the other hand priority defines the order in which we should fix a bug. Should the bug be solved now or later?
Both severity and priority go hand in hand. Following are some of the important scenarios related to severity and priority.
1. High severity and high priority: Bug that affects the functionality of the system and does not allow the user to proceed further. One simple example is that the system crashes on the login page. This bug has a major impact on the system and needs to be fixed at the earliest.
2. High severity and low priority: System crashes on click of a save button which is a part of next release. This bug has a major impact on the system but since the save functionality is a part of next release, the priority assigned to this blog may be lower.
3. Low severity and high priority: An example of such a scenario is a spelling mistake in the company name. This bug will allow the user to use the system but it has a major impact on the company’s reputation. Such bugs are not acceptable and need to be solved on a high priority.
4. Low severity and low priority: Minor UI issues are examples of low severity and low priority.
Of course, there are other factors that affect bug fixation. Most of the times bug severity and priority have to be assigned by a project coordinator or tester. However, when a module or the entire software has to be deployed to the customer, severity and priority has to be assigned keeping the customer’s point of view.
– Dixita Dessai