With Calleo, you get expert guidance to find the right options, demos and trial licenses to evaluate them, and practical help to get up and running. You’ll see the pros, cons and long-term costs clearly before making any decisions, and stay supported with renewals and updates long after you’ve started using the tool.
Automation maintenance is a pain. It’s a frustrating time drain that nobody enjoys. Unfortunately, teams are doing more of it than ever, with modern solutions changing like the wind and each new release jeopardising script integrity. Thankfully, AI-driven automation is here to help.
Thanks to your support, 2025 was another excellent year for Testing Times and our 10,000+ subscribers. We explored a wide range of software testing topics, including test automation, performance testing, Jira fatigue, tester authority, and more. Below is a quick look at the five newsletters with the most reactions this year, and why they resonated so strongly.
Increasingly, organisations expect remote and hybrid testers to use borrowed tool licences, unstable VPNs, and software never designed to leave the office. That creates significant compliance and security risks that can turn into serious long‑term problems. It’s not the testers per se, but remote execution over on‑prem licences is a software audit waiting to happen. Read on to learn why a compliance nightmare isn’t the only reason your test setup might not be fit for distributed and home‑working team members.
Software teams know the story all too well: automation promises speed and reliability, but reality often brings fragile scripts, phantom failures, and endless rework. In the end, the technology intended to accelerate releases ends up bogging things down. Or at least, that’s how things used to be… Today’s AI-powered functional
Testers have long been asked to test earlier, faster, and more often. In truth, however, when critical APIs, integrations, or microservices aren’t ready, testing gets stuck. We’ve all been there, raring to go, like greyhounds in the slips… but with nothing to test, and increasingly concerned about the impending last-minute panic.
During the 2008 credit crunch, companies slashed technical investment. The mantra “do more with less” stuck—and 17 years later, testers are still paying the price as demands, complexity, and expectations have soared. It’s no coincidence that we’re witnessing an increasing number of high-profile software failures and cyber attacks. Yet, there’s still little willingness to invest in the right test tools and training.
Many small software teams turn to test automation, expecting substantial time and cost savings. However, they often fail to achieve any of these goals; instead of seeing a return on investment, they end up spending more effort and cost fixing their automation packs. This failure can leave lasting scars, deterring people from embracing automation and realising its many benefits…
I often speak to people who want to abandon legacy test tools and transition to shiny new solutions. They cite several reasons for the switch, many of which are valid, while others need greater consideration to avoid a negative or costly outcome. On the other hand, I also speak to people who are reluctant to ever change tools, even though they’d see incredible benefits.
Shift-left testing has become one of the most talked-about software development ideas. It sounds deceptively simple: test earlier in the process to avoid late surprises. But while the phrase is repeated at countless conferences and stand-ups, it is often misunderstood, misapplied, or reduced to a box-ticking activity (like many other testing initiatives).
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.
