Sometimes triggering a bug takes the perfect storm of the right (or wrong?) web browser, browser version, OS, screen dimensions, device…Because testing can never cover everything, it’s possible that you’ll never hit that specific bug-triggering combination. When that happens, a bug may slip through to production and stay hidden until a user discovers it “in the wild.”
Ah, the backlog! It’s supposed to allow us to keep track of all of the bug fix tickets so we can prioritize them and work them into the sprint or project plan.Although we have good intentions when we create a follow-up issue to resolve a bug, unfortunately sometimes the backlog is like the Island of Misfit Toys. These tickets are created, dropped in the backlog, and forgotten – and thus, their bugs are forgotten too.
With the tension between testers and developers that plagues some companies, it’s not always easy to point out a bug. In fact, it can be downright intimidating. This is be even more true when the tester is new to the testing craft or new to the team, or when the developer is a highly respected senior programmer.If a tester notices a bug – or even just a possible bug – and doesn’t mention it, the chances of getting that issue resolved are pretty slim indeed.
4. Another bug obscured it.
Few things are as effective at hiding a bug than another bug that prevents you from triggering it or reaching it in the first place.Say you’re testing a new feature. Things seem to be going well, but suddenly you reach a point where further testing isn’t even an option because of a bug. For example, maybe you need to click a link to actually use that new feature, but the link isn’t there at all.You’ll have no way of knowing that there’s a problem with how that new feature works on a mobile device if you can’t even get the new feature to appear.