I was demoing some software when I said “I found a really cool bug”. I was quickly questioned why the action of finding a bug would ever be really cool, or why the bug itself would be cool. How could either of those scenarios be a cool thing?
The act of finding bugs is what I do. As a QA tester, my daily duty is to dig deep and find any possible bugs that may exist in our software prior to sending it out to the public. While I don’t always enjoy finding the basic bugs such as alignment, spelling errors, or page load problems, there are times where I find a bug by doing some deep-dive exploratory testing.
The acceptance criteria of any new feature cannot possibly state all the scenarios and workflows that could exist. There are times that the list for that would be so long, it wouldn’t be worth the time to write it all down. For those scenarios, it takes a good tester who knows the product and workflows, and desires testing them all. Through exploratory testing, we can find those bugs that may only exist in that particular workflow, and therefore the action of finding and reproducing them is really cool.
There are times that a bug itself could be really cool. Not that any bug is ever actually cool, because it comes with risk, but again, as a QA tester, I sometimes come across bugs that excite me a little to log. They don’t include a difficult workflow, they are plain and simple, and sometimes reveal themselves just by logging in to the software. But, what makes these bugs cool is the feeling that I get when logging them.
Often these bugs are data configurations or a special setup that I may have that others wouldn’t because of experience or sheer luck. Sometimes these bugs boost confidence for the testing efforts and remind me that there are lots of opportunities to find more. Other times I’m working with a great developer who is so overly confident (often jokingly) in their work, that they swear by no bugs.
Whatever the reason, it’s cool to find these easy ones sometimes, because not only do they help the overall product, but they help me as a tester become more aware, be a better exploratory tester, and build further relationships with my developers.