How the Robot Framework Journey Started with 7000 Test Cases

How do you build a test automation framework used by millions? Pekka Klärck, lead developer of Robot Framework, reveals the design decisions that created one of the most powerful open source testing tools. "I'm allowed to say that they are badly designed because I've designed them." - Pekka Klärck In this episode, I talk with Pekka Klärck about Robot Framework. We start with 2004, his thesis roots, and Nokia Networks turning a prototype into an open source project in 2008. He explains the core idea: a generic engine with reusable libraries, human readable tests, and one set of reports. Best fit in mixed tech stacks. We revisit milestones like the move to plain text, a new parser, and a thriving ecosystem. Pekka previews secret variables in 7.4, a modern user guide, markdown docs, and a cleaner namespace with backward compatibility. He even tests Robot Framework with Robot Framework. 00:00 Origins of a Generic Framework 06:33 Streamlined Automation with Robot 09:11 Evolution of Parsing and Editing 11:24 Impact of Listener API Changes 16:56 Robot Framework: Markdown Coming? 20:07 Maintaining Quality Over Speed 22:27 Promoting Awareness of Robot Framework 27:03 Popular Conference with Great Atmosphere 28:21 Conference Location Strategy Update 📘 Free e-book: The 7 success factors of software testing. 25 years of project experience in one 33-page workbook, now also in English 👉 https://tul.fm/ebook 🎯 Highlights: Robot Framework's generic core handles parsing, execution, logging, and reporting uniformly, so teams only need to solve the interface-specific problem for their own system. The ecosystem of editors, libraries, and integrations carries more practical value than the core framework alone, and it grows independently of Pekka Klärck's direct involvement. Robot Framework fits heterogeneous environments best; for a pure web project where the whole team writes TypeScript, a native tool like Playwright is likely the better choice. Close to 7,000 Robot Framework test cases are used to test Robot Framework itself, including cases where unit testing tools would technically be the more conventional fit. The Robot Framework Foundation has over 80 member companies, yet far more companies use the framework without contributing financially, which puts the long-term sustainability of paid core development at risk. 🔗 Links Blog Post for Episode: https://www.richard-seidl.com/en/podc... Win a free Ticket for RoboCon 2026: https://seu2.cleverreach.com/f/362604... RoboCon 2026 Discount Tickets: https://tickets.robotframework.org/ro... 🎙️ More from Richard Seidl Website: https://www.richard-seidl.com Linkedin:   / richardseidl   Podcast Software Testing: https://www.testing-unleashed.fm #softwaretesting #QA #robotframeworktutorial