As soon as I saw this news piece a bunch of bugs suddenly appeared right in front of him, I'm really not quite sure how that happened.
A certain type of bug kept appearing in various places on our website. It was related to text size appearing too big. Rather than trying to explain it each time I saw it, I called it 'Big Text Syndrome'.
Maybe giving a re-occuring software bug a name can help us better communicate the issue to people within the team.
How many times have we run a testing session to discover a bug we just had no intention of or idea that we might discover it? The joys of testing, right? Some of my favourites are when you're retesting a bug fix and another bug pops up to say hi. Hello little bug! There have also been times in my career when I've worked with a developer who was so good at convincing me that I hadn't discovered a bug. It was a real Jedi skill. I'd walk back to my desk, confused and convinced it was a bug whilst also questioning my testing skills.
We've probably all experienced "that look" that people give you when something goes wrong.
I've lost count of how many times I hear a random person say, "Why doesn't this thing just work!" It's tiring. Yet I also have an internal wry smile thinking that we testers will continue to improve the world of apps. AI whatever, we'll be alright. 😉 Happy World Testers Day!
It's very easy to be critical, raise bugs and give feedback that doesn't help a team move forward. Always ask yourself if your work will be of value and good use of time, because time is money.
