Test automation works when it solves real problems, not when it focuses on tools. The focus shifts to why, where, and how. The test pyramid places checks at unit, API, and UI levels so feedback stays fast. A gaming product with 5000 defects and falling velocity shows the cost of weak strategy. A lean roadmap, six month checkpoints, and measurable value reset direction.
In this episode, I talk with Péter Földházi about test automation that solves real problems, not shiny tools. Péter brings two decades in quality and helped write the ISTQB automation syllabi. We ask why to automate, where it fits, and how the test pyramid guides choices across unit, API, and UI. I like how the simple pyramid makes choices visible. He shares a gaming case with 5,000 defects and a velocity drop. Strategy first, then tools, six month steps, and clear value.
"But ultimately what matters is: what is the problem that we are solving and, and what is the architecture." - Péter Földházi
Péter was first involved with QA as a beta tester of DOTA in 2006. Since joining EPAM in 2012, he moved towards test automation, and is currently working in the USA as a Quality Architect. He is leading Game Testing Consulting and GenAI Adoption programs in the Americas.
Péter has authored two ISTQB syllabi: Test Automation Engineering & Test Automation Strategy. He also invented two test automation methodologies: the Flow Model Pattern and the Tri-Layer Testing Architecture, the latter published as a white paper by the PNSQC. Péter has been one of the review board members of the HUSTEF since 2015.
Péter is a regular keynote and tutorial speaker on conferences such as STARWEST, STAREAST, and SauceCon. He used to be a guest lecturer at 3 Budapest based universities: Óbuda, Pázmány and the ELTE. Brewing beer and planting chilis are some of his hobbies.
Test automation has become a buzzword in software development—often seen as a silver bullet for improving speed and quality. But as Richie and Péter Földházi discuss in the latest episode of Software Testing Unleashed, effective automation is about much more than just buying the latest tool. Their conversation—recorded live at Budapest’s Gustev Conference 2025—dives into the real challenges, strategies, and future directions facing teams today.
Many organizations fall into the trap of adopting automation technology simply because “everyone else is doing it.” Péter stresses that real success starts with understanding the problems you aim to solve. Teams must ask: What value will automation bring? The mistake often made is focusing first on tools (and sales pitches), rather than strategy.
Case in point: Péter shared a story about a gaming company plagued by thousands of defects every month. Their automation strategy wasn’t just about catching bugs; it was about reducing the burden of defect fixing and improving overall product velocity. The end goal? Find issues earlier in the lifecycle and increase resolution rates, freeing time and resources to build new features.
Once your objectives are clear, how do you map out a path forward? Péter recommends starting with an assessment—understanding where automation fits at each level in the “test pyramid”:
Unit tests (code-level coverage)
Service/API tests (contract and integration points)
UI tests (end-user journeys)
Visualizing current coverage and gaps helps even non-technical stakeholders see where defects and costs spiral. From there, craft a strategy for the next six months—focusing on realistic, high-impact improvements (not chasing an “ideal” pyramid shape).
A good strategy is custom to your project, but the principles remain the same: leverage existing strengths, fill obvious gaps, and don’t overengineer. The right balance saves both time and money.
Tool selection comes after the strategy—not before. As Péter puts it, being “tool agnostic” allows you to focus on project needs. Maybe a longstanding team works best with Selenium. For newer stacks, Cypress or Playwright might fit. The main point: Choose the tool that solves your problem, not the one with the flashiest demo.
Péter also clarified some common terminology—generic test automation architecture (GTAA), test automation architecture (TAA), framework, and solution—drawn from ISTQB syllabi. Here’s the difference:
GTAA is a blueprint: What should any framework provide?
TAA is your concrete design: Specific for your company, project, or team.
The solution is the implementation: Building out the architecture in code, connecting tools, and integrating with pipelines.
The framework governs the test scripts, business logic, and core libraries.
Understanding these layers helps teams avoid confusion, streamline processes, and communicate better across roles.
Automation doesn’t work in a vacuum. Successful teams collaborate across testing levels—developers, testers, product, and operations. Unit, API, and UI tests each add unique value. Shared goals and visibility (the “test pyramid” view) mean teams avoid duplicate effort and spot issues faster.
Will AI take over the automation process? Not yet. While tools advertised as “AI-powered” are common, Péter cautions that true agentic capabilities—where intelligent agents handle repetitive tasks or generate test cases—are just emerging. Human expertise remains vital, especially for configuration and adaptation.
Next-generation IDEs and platforms are making AI agents increasingly accessible, potentially boosting productivity and freeing up tester creativity. But as Richie notes, predicting the future is tricky; success depends on combining technology with human insight.
Ready to start automating? First, assess your team’s strengths and experience. If no one has an automation background, invest in upskilling or bring in an expert. Starting without the right knowledge is costly and risky.
Then, define the problems you want to solve. Map your current test coverage. Start small, deliver value early, and expand as you learn. Above all, focus on solving real problems—not implementing tools for their own sake.
Test automation is evolving, but its fundamentals remain rooted in strategy, collaboration, and clear business value. With AI on the horizon, teams that blend technical expertise with thoughtful planning will continue to drive real software quality. As Péter urges: Prepare not just for today’s trends, but for tomorrow’s breakthroughs.