30/10/2026
Anti-Bug Birthday: QATestLab turns 24🎂
That’s long enough to watch software testing change several times. For our birthday, we decided to look back at how the bug report evolved while we were busy writing them.
🖥️ The desktop years. Many bugs could be reproduced on a specific desktop setup, and a typical report read “The app crashes if you click Save twice”. A good part of every project went into checking which Windows versions the product really supported.
🌐 The browser wars, seen from QA. The same page could work perfectly in one browser and break in another. Cross-browser testing became a daily routine, and the first automation tools slowly took over the repetitive clicking.
📱 The smartphone era. Growing variety of screen sizes, OS versions and network conditions appeared almost overnight. We started testing what real users do with their phones, including the incoming call in the middle of a payment that nobody wrote into the spec.
🎮 Games, TVs and connected devices. We started finding bugs in unexpected places: TV remotes, save files 40 hours into a game, firmware that updates at night.
🤖 The AI years. Today a product can respond to the same prompt in two different ways, and both versions may sound convincing. There is no crash and no stack trace to point at, so testing starts with defining what a correct answer looks like.
What stayed the same after 4000+ projects?
A bug that can’t be reproduced remains the hardest one to fix. The best testers wonder “what if the user does this?” before anyone else thinks of it. And every team, ours included, has called a bug a feature at least once 😏
The cake was the only thing we promised not to test today 🍰 Out of professional habit, we ran a quick smoke test anyway.
Thank you to our clients, partners and team for being with us since our very first project 💙
Which bug from your career stuck with you for years? Tell us in the comments, we read every story 🐞