Products

Problems
we solve

We can help your business

Request a Free Demo / trial

Insights

Insights
6 August, 2025

Are Test Automation Claims Just Marketing Hype?

Test Automation Hype

Read the marketing collateral from test automation vendors and you’ll encounter bold promises around costs, coverage, and defect reduction. However, for many who have been through multiple automation initiatives, the reality frequently fails to live up to the pitch.

It’s no surprise, then, that these claims spark a healthy dose of scepticism within both the testing and developer communities.

This begs the question: Are all test automation claims just marketing hype?

Teams Often See Disappointing Results

I have been involved in software testing for over thirty years and have been a strong test automation advocate for a large part of that. However, I am also the first to admit that many test automation initiatives fail to deliver the promised time or cost savings.

The frustrations are common: ongoing and unexpected costs, endless hours spent maintaining flaky scripts, and dubious test results that undermine trust in automation.

It is entirely fair to say that, on many occasions, test automation costs more than it delivers. This leaves teams and stakeholders wondering if it was worth it, and puts them off future automation initiatives.

Common reasons why automation efforts underperform include:

  • Poor Tool Selection: Teams select tools that are too complex to use, lack support for key applications, and are generally ill-suited for their business landscape and internal policies.
  • Ignoring Total Cost of Ownership: Tools are chosen based on upfront cost rather than total cost of ownership (TCO).Upfront licence costs are only part of the equation. Ongoing maintenance, integration, and infrastructure costs add up quickly and can erode long-term value.
  • Ineffective Implementation: Rushed rollouts, no pilot phase, or limited stakeholder involvement result in poor fit and low value.
  • Misunderstanding Automation’s Purpose: Some try to automate tasks that are constantly changing, such as unstable applications, volatile UIs, or early-stage projects.
  • Neglecting Skillsets: Underestimating the learning curve required, or failing to invest in upskilling, leads to inconsistent and unreliable tests. it can also lead to an over dependence on consultant or contract resource which will increase cost.

The Times When Automation Does Deliver

And yet, test automation can deliver on its claims. I have seen it, many times.

As I said earlier, I am a strong automation advocate. I have seen companies accelerate development, increase quality, and change their whole outlook on testing through the use of effective automation. But it has to be done correctly.

Automation can yield game-changing ROI, but only if it’s taken seriously, deployed thoughtfully, and treated as a serious project in its own right.

As with any other project, in any field, the benefits of test automation can only be realised when automation is:

  • Matched to Clear, Achievable Goals: Focused on stable, well-understood, high-value areas that change infrequently.
  • Implemented with the Right Tools and Skills: Tools like OpenText Functional Testing (formerly UFT One) make automation accessible with broad language support and extensible plugins, making them easier to integrate into diverse teams.

Six Steps to Unlock Genuine Automation ROI

Automation can and will deliver benefits, and here are six steps to help you make it happen:

  1. Start Small: Run pilots on contained, high-value workflows. Validate the approach before scaling automation broadly.
  2. Match Tools to Team Skills: Choose tools your team can quickly pick up and adapt, such as OpenText Functional Testing. This lets you automate across a broad tech stack without steep learning curves.
  3. Focus on Maintainability: Robust scripting practices, modular test design, and AI-assisted maintenance to reduce flakiness and rework.
  4. Automate What Matters Most: Concentrate efforts on smoke tests, regression suites,  and business-critical workflows.
  5. Invest in Upskilling: Don’t just get a tool and expect your testers to use it. Dedicate real time to mastering both its features and automation best practices. This investment saves money in the long term.
  6. Continually Reassess: Regularly review and optimise your test automation suite to ensure the tests remain relevant and aligned with genuine business needs.

Conclusion

You may have been burned before, and of course, it’s wise to treat outlandish marketing claims with a pinch of salt.

However, with a strategic approach and the right tools (such as OpenText Functional Testing), automation delivers measurable, sustainable returns and keeps your QA operation lean and effective.

Related Products

UFT One
Stephen Davis
by Stephen Davis

Stephen Davis is the founder of Calleo Software, a OpenText (formerly Micro Focus) Gold Partner. His passion is to help test professionals improve the efficiency and effectiveness of software testing.

To view Stephen's LinkedIn profile and connect 

Stephen Davis LinkedIn profile

6th August 2025
Adding More Testers Makes Quality Worse

When Adding More Testers Makes Quality Worse!

You’re deep into a project, go-live is rapidly approaching, but there is a mountain of testing to get through. Then, a key stakeholder chimes in, “Let’s just pull more people into testing.” It sounds logical: bigger effort, higher quality. But doubling down on resources can easily lead to chaos, confusion, and worse software quality.

Is Open Source Trustworthy

Do You Trust Open-Source Tools for Enterprise Testing?

Open-source testing tools like JMeter and Selenium have obvious appeal—no licensing fees, endless customisation, and a community to lean on. But, if you’re using open-source for mission-critical testing, you need to ask—is it really worth the risk?

Should testers be allowed to block releases?

Should Testers Be Allowed to Block Releases?

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?

Bug seeding

Bebugging: Would You Plant Defects to Test Testers?

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?

Unethical Test Tool Marketing

Exposed: Are You Being Conned By Test Tool Marketing?

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.

Flaky Automated Tests

Are Flaky Automated Tests Better Than None at All?

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?

Software Testing Concepts

Software QA Mythbusting: 5 Misunderstood Testing Concepts

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.

LoadRunner v JMeter

LoadRunner: Cheaper & Easier Than JMeter?

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.

Model Based Testing

How to Bridge the Gap Between Business and Testing

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.

Insights

Search

Related Products

UFT One

Related Articles

InsightsTrending

To get other software testing insights, like this, direct to you inbox 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.

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.