Your testers find a critical bug the night before a major release. Should they have the power to stop the launch?
Testers provide essential insights into software quality and risk. Their analysis is critical for decision-makers, so would it make sense to give them the power to veto releases?
Would you intentionally plant defects to test your test team? Bebugging, as it’s known, is a technique where software flaws are purposely introduced to gauge testing effectiveness. Are there times and places where bebugging is a valid way to help improve processes, tighten up testing, or root out a potential weak link?
We have all witnessed an alarming rise in deceptive marketing practices that undermine customer decision-making and market integrity, with tool vendors increasingly comparing their tools to industry leaders using deliberately misleading information.
Is flaky automation better than no automation at all? Does it help accelerate projects and reduce timelines, or does it end up causing more problems than it solves? And are the questions moot when, with modern AI-powered tools, there’s no excuse for flaky tests?
We’ve all been there—sitting in a meeting, nodding along, confident that everyone shares the same understanding, only to discover later that our ideas were built on shaky ground, based on false assumptions and an incomplete grasp of a complex situation. In the world of software development, nowhere is this more common, or more consequential, than with software testing.
Four years ago, I wrote about how LoadRunner Cloud was debunking the myth that open-source is cheaper. At the time, LoadRunner Cloud’s pay-as-you-go pricing, bundled infrastructure, and rapid setup were already making it a compelling alternative to JMeter and similar tools.
MBT can transform software QA processes through enhanced collaboration between testers and subject matter experts (SMEs). It offers enhanced capabilities for businesses seeking efficient, comprehensive testing solutions in an increasingly complex software landscape.
Are you sick of Jira test management solutions? You’re not alone. I speak to dozens of businesses monthly across all different sectors. Many have been forced to use Jira for test management. The more positive people I talk to say it is okay at best.
After decades in the software industry, I’ve witnessed firsthand how six fundamental principles consistently drive software testing success regardless of methodology or domain. Whether you work in functional or performance testing, follow Waterfall or Agile, or specialise in manual or automated testing, these guidelines form a checklist for consistent testing success.
OpenText’s performance test tools—formerly the LoadRunner family—are continuously improving. Over the last few years, they’ve been enhanced with new features to help your teams deliver responsive, resilient applications with an excellent user experience.
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.
