Which bugs are you proudest of finding in TEST (not in production)?

We see a lot of news about issues that make it into production.

What about the ones we find BEFORE they wreak havoc in the wild? This community must have a ton of stories.

Which bugs are you proudest of finding during testing? Put another way, which bug is your favorite to tell others about finding?

  • What kind of software?
  • How did you find it? Scripted test? Exploratory?
  • Why is the bug your favorite one to talk about?
3 Likes

Bugs where my knowlede of how all the systems work together becomes necessary.

2 Likes

My proudest finds are ones where the scenario was thought of while doing the testing. Moreover, the scenario was not part of the original plan.
Sometimes, I write some obvious yet very loosely related stuff in my test plans which later turns out to be a bug. That makes me proud too.

2 Likes

I love the password bug we found with our automation when the code was still in development.
Suddenly one of our standard tests failed because a password was gone. I was sure I had set one, so I reset the database and ran the test again. Afterwards the password was gone again. Brought up the issue to the dev working on the new password encryption process. This bug never made it out of the development phase.
It really proved our automation approach to the team. With the database reset we could easily show the password disappearing. The simple automation of an β€œunrelated” component flagged a major issue early in the process.

2 Likes

Nice. I recently found a file save bug in an application in a similar way: the file’s contents were deleted completely but only if I’d chosen a certain file format for the save! Took a few tries to root-cause that one.

1 Like

requirements bugs

those are always the best ones to unpack while testing and before anyone even wastes time with a demo.

2 Likes