Confused tester

What Do You Mean You Didn’t Find A Single Bug?!

So there was this one time I came across a curious statement in my team after a little testing session: there are no defects here, Peter (let’s call him Peter) stated. This very statement looked so absurd and impossible everybody literally froze. It’s not that Peter was a bad tester, no, he is great at what he does. It’s just that we were shocked with this reality falling on our unrespecting shoulders literally crushing and devastating our entire way of thinking.

What was the case?

You know what? There are times you can’t find bugs, most of them, like 99.9% happen because you have done something wring while testing, but there are unique cases. Here is what we dealt with: our developers were implementing a small feature and they were astonishingly well with both coding and their share of testing. Plus the environment was closely controlled, literally obliterating all chances for any bugs of some importance to emerge. But, however that is a one in a million case that happened right there and yet it got me thinking, are there any other cases where testers are not finding defects for a reason?

Other cases

Bugs are of no importance to you. It’s not that you don’t care or anything of that sort. You may be providing some load testing service and all is great with that part, but bugs that relate other aspects still exist. They are simply pot of the scope.

There was one more interesting scenario I have encountered common to paired testing. Developers write code and testers track and point out bugs, they are instantly fixed before any bug reports are created whatsoever.

The worst case scenario is when a tester just shouldn’t be testing software due lack of skill and a poor mindset not fit this job. And while skill may be gained, a mindset is something testers are born with. Great testers I mean. This mostly happens due gaining popularity of QA professionals and way too many people want a slice of the pie, whilst they believe decent money are paid for doing nothing. However this matter requires a different post or even an entire book about how ridiculous such an approach is.

Have you encountered cases when you have faced no bugs in the code? Share your experience!


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


2 comments

  1. May 28, 2015 @ 10:17 pm Andrew Wilkins

    Hi BugHuntress,

    I’m not sure if you did this on purpose to test true QA people, but there are some mistakes in your article. But besides that I agree with you, being a Software Quality Assurance Analyst myself, and being in the QA business for 3 years now. I can say that people do have a misinterpretation about the job that I do. Many people want to say that it is easy and I get paid a lot to do nothing at all. This is never true. I’ve worked for companies such as Brook Furniture, Motorola, and Samsung. When it comes to being QA there you are in a very volatile position. There are times when work is a little slow, but in those times you are expected to become more technical in your work. Get an understanding of what the developers are doing. Maybe expand upon your knowledge of SQL. Those times are few and far between depending on the size of your company and the scope of your team’s work. I know you know this as much as anyone else in the QA business. One thing I never see mentioned here but does happen frequently in the corporate world of QA testing: Being the scapegoat. When things don’t go the way that they are expected to, it is a very common and bad practice to blame the QA person. I myself have really only been in the scenario once but I learned a lot from the experience. This is a very heavy burden to carry because when the time for blame comes, they start with us first….which leads back to the thinking of our jobs being easy and not really doing work. It seems businesses are realizing how are roles are more important nowadays but the axe still swings low and fast…


Would you like to share your thoughts?

Software testing & QA blog by TestFort © 2017

×