Software Testing Unleashed - QA, DevEx & Quality Engineering

Do your tools fit your real needs? - Mesut Durukal


Listen Later

Switching End-to-End Test Automation Frameworks: Lessons from Real-World Projects

๐Ÿ“˜ Free e-book: The 7 success factors of software testing. 25 years of project experience in one 33-page workbook, now also in English ๐Ÿ‘‰ Get it for free

"If we go with the wrong tools or wrong alternatives, then we might not be able to cover everything that we are supposed to do." - Mesut Durukal

In this episode, I talk with Mesut Durukal about picking the right end to end test automation framework. Mesut shares why tool choice must serve real needs, not trends. It is a mindset shift from hype to needs. In his case users were on Safari, the team tool did not run there. He mapped needs, compared Cypress, Playwright, Selenium, TestCafe, and Nightwatch, and chose Playwright for speed and broad browser support. We talk about reporting, debugging, and docs. We touch on architecture, like keeping login and helpers outside specs, so migration stays clean. For me, this is tech with agility. Know your goals, grow your system, and review choices often.

Mesut has over 15 years of experience in areas such as industrial automation, IoT, cloud services and defense industry, complemented by his expertise in test automation and CI/CD integration. He has held multiple roles in multinational projects including Quality Owner and Hiring Manager and is well versed in CMMI, Scrum & PMP. As a recognized speaker on international stages and winner of the award for the best presentation, he is also involved in various program committees.

Highlights:

  • Safari browser support was the decisive failure point that forced a tool migration: the existing framework could not run tests on the most-used browser in the target market.
  • Defining required features before evaluating tools, not after, is what separates a structured tool selection from a trend-driven one.
  • A well-architected test suite with shared helper classes instead of duplicated spec files makes framework migration significantly faster, because reusable functions are framework-agnostic.
  • Playwright outperformed the alternatives on execution speed and Docker image size, while Cypress offered stronger built-in reporting and an integrated visual test runner.
  • ...more
    View all episodesView all episodes
    Download on the App Store

    Software Testing Unleashed - QA, DevEx & Quality EngineeringBy Richard Seidl | Software Development & Testing Expert