Ah, software testing—where meticulous planning meets unexpected chaos and where even the most rigorous quality assurance can sometimes go awkwardly awry. As we bid farewell to 2024, it’s time to take a step back and indulge in some light-hearted reflection on the quirky side of our profession.
The World Quality Report (WQR) 2024-25 looks at the current state and future trends of Quality Engineering—albeit from a particular perspective. It is based on a survey of 1,775 executives across multiple sectors and regions. While it is a potentially interesting source of information, I’m always left asking the question: Is it useful?
Here’s a universal truth: Within minutes of a solution going live, the user base finds unexpected ways of using it. This is applicable across the board, from large-scale ERP implementations to websites, from graphic design software to video games.
In my latest Testing Times newsletter, I discussed Microsoft and their poor software quality. This led to a couple of conversations on LinkedIn comments concerning Microsoft’s approach to testing… and whether developers should ‘test their own homework’ as the saying goes. Click the newsletter link to read the comments in full.
You think you’ve found the perfect tool that ticks the speed, coverage, flexibility, support, and cost boxes—but there are good reasons to think again.
Microsoft (MS) has dominated the software landscape for decades, boasting vast resources and some of the brightest engineering minds. Yet, despite this wealth of talent, many users struggle with persistent issues that raise questions about the company’s commitment to quality and customer satisfaction.
What if I told you that, despite your best efforts, your brain could be sabotaging your testing approach? And that while you’ve spent your entire software testing career trying to find the biggest, juiciest bugs, your subconscious has had other goals altogether?
The Post Office Horizon scandal destroyed lives and livelihoods and is rooted in defective software. This insight looks at the scandal from a testing perspective and serves as a cautionary tale for all involved in deploying large-scale IT systems.
When considering the procurement of software tools, there is often a common misapprehension: Open Source = Free = Economical. But is it that simplistic?
Software testing, like all human activities, can have ecological consequences. This insight includes eight ways you can reduce the environmental impact of software testing and shape a greener future.
Sign up to receive the latest, Software Testing Insights, news and to join the Calleo mailing list.
You can, of course, unsubscribe at any time!
By signing up you consent to receiving regular emails from Calleo with updates, tips and ideas on software testing along with the occasional promotion for software testing products. You can, of course, unsubscribe at any time. Click here for the privacy policy.
