10 Reasons to Fix Software Bugs Right Away
Adventures in QA came across this great infographic by Andy Glover (Cartoon Tester) and Matt Archer that beautifully illustrates why you should fix a bug a soon a you find it. The infographic is quite big so here’s a quick overview of the reasons they list:
- Unfixed bugs camouflage other bugs
- Unfixed bugs suggest quality isn’t important
- Discussing unfixed bugs is a waste of time
- Unfixed bugs lead to duplicate effort
- Unfixed bugs lead to unreliable metrics
- Unfixed bugs distract the entire team
- Unfixed bugs hinder short-notice releases
- Unfixed bugs lead to inaccurate estimates
- Fixing familiar code is easier than unfamiliar code
- Fixing a bug today costs less than tomorrow
Check out the full infographic for illustrations and the reasoning behind each point.
Unfixed bugs irritate testers and make them feel as if testing efforts are not so imporatnt
Unfixed bug shows poor defect advocacy
unfixed bugs creates an unwanted problem.
Fixing a bug today costs less than tomorrow!
Cost of Fixing a bug increases with the Software Lifecycle progresses, thus fixing them is important as soon as they are found. Secondly, One bug may be masking another bugs, which may lead to unexpected behavior. So, these 2 are the most important reasons to fix a bug as soon as its found.
Unfixed bugs is a pain for testers as they have to search for duplicate bugs before reporting a new bug. If the number of bugs is huge, the risk to report duplicate bugs is higher. Thus, it is also a waste of time.
First check the spec to stop rework because ambiguity equal bugs.
Fixing bugs keeps the service department happy and not pleading for help.
So now the question is: why bugs aren’t fixed?
- lack of resources, time
- non-liability of software developers
- …
Fixing bugs shows that customers are important!
Get free Aquarius Horoscope and Aquarius Astrology report of every month such as January, February, March, April, May, June, July, August, September, October, November and December from Indastro. We provide Aquarius horoscope report based on moon signs.
Great infographic – the best way to fix bugs is to let the developers catch them as they develop, with developer testing such as unit testing.
Typemock has a great infographic that you should check out: http://www.typemock.com/blog/2012/07/18/the-severity-of-bugs-are-we-doomed/
If I had infinite resources I’d fix all the bugs. One of the reasons we do content planning and use our configuration managment features like branching is to enable management decisioning making that is as “late” bound as possible. Bugs get fixed according to priority/severity/risk and best use of scarce resources. This utopian dream is not commercially realistic. Also this article seems to be about “fix” all but ends up talking more about “find” all. This is a confused aim.
unfixed bug is seems to be like closed Door that don’t know or expect what is behind
Here’s the original source – http://www.thetestingplanet.com/2012/07/10-reasons-why-you-fix-bugs-as-soon-as-you-find-them/