February 19, 2026

Why Test Automation Needs Design Patterns - Kostiantyn Teltov

19 minutes

Page Objects, Builders, and Facades: Key Test Automation Design Patterns Explained

🚀 Do you like the podcast? Then please rate and share it. And feel free to send feedback to [email protected]

"Design patterns support extensibility of our test automation solutions." - Kostiantyn Teltov

In this episode, I talk with Kostiantyn Teltov about design patterns in test automation. Kosta shows why test code needs the same care as product code. Page Object to cut duplication. Builder to shape data like choosing a burger. Facade as a reception that guides you to the right service. We touch creational patterns and even pools for drivers. DRY, KISS, and YAGNI keep us honest and stop overdesign.

Kostiantyn Teltov was born in Dnipro, Ukraine, and lives in Kraków, Poland, for the past three years.

He has been working in software testing since 2008 and writing code for over 11 years.

His technical background includes C#, Java, JavaScript/TypeScript, and Python, and he can speak four languages — though not all my programming and speaking languages are equally good ;-)

He is a strong advocate of the Shift-Left testing mindset and the Testing Pyramid approach.

He is passionate about mentoring and educating others, especially in Test Automation.

In the past, he has lectured IT courses. Today he speaks at webinars, meetups and perform workshops, and regularly write articles on Medium.

Currently, he works as a QA Lead at Metso, managing five projects and focusing on building QA processes and automation frameworks with limited QA resources.

Highlights:

Test automation code needs design patterns just like production code to prevent spaghetti architecture.

Page Object, Builder, and Facade patterns are essential for readable, maintainable test frameworks.

Design patterns enable common language with teammates and support framework extensibility as solutions scale.

AI generates test code only when explicitly prompted with context, still requires human verification.

DRY principle prevents code duplication; KISS and YAGNI avoid overcomplicating what you don't need.