The Maintainer's Journey: Robin Mackaij on Taking OpenApiDriver from Internal Tool to Open Source

We've all done it. That one little keyword, that one helper script, that "quick-fix" Python library that solves a very specific, nagging problem. It works. Your team loves it. It grows. And then, someone in a meeting says, "You know... we should probably open-source this."

Easy, right?

What happens when that "little script" grows up, moves out of the house, and has to survive in the wild world of open-source?

If you're a regular in the Robot Framework community, you probably already know Robin Mackaij. He's an experienced test automation engineer, a Python developer, and a familiar face as a RoboCon regular, speaker, and workshop host. More importantly, he's the author and maintainer of the OpenApiDriver and OpenApiLibCore. He's exactly the person to tell this story.

From Internal Fix to OpenApiTools

We're thrilled to have Robin hosting a workshop at Wrobocon titled, "A (semi)short history of OpenApiDriver: from internal library to OpenApiTools."

This isn't just a "how-to" session; it's a "how-it-happened" story. Robin will pull back the curtain on the complete lifecycle of a tool many of us rely on. How does an internal library get created to solve a problem? What's the tipping point that leads to open-sourcing it? And, crucially, what happens after it's released to the public? (Hint: it involves a lot more than just hitting "merge").

Robin will trace the design and architecture of the library as it evolved from its first internal release to its current form as part of the OpenApiTools ecosystem.

More Than Just a Story: A Technical Deep Dive

This session is a case study for any developer or automator who has built, maintained, or considered building a custom library. Robin is ready to get into the nuts and bolts.

Topics will include:

• Packaging & Distribution: The real fun, right? How to get your tool into the hands of users.
• Build vs. Buy: The eternal engineering debate—when to use other packages versus when to roll your own implementation.
• Smart Subclassing: A look at the design patterns used, including a friendly hat-tip to DataDriver.
• The Robot API: Leveraging the Robot API for advanced library development.
• Testing the Testers: How do you effectively test your own custom Robot Framework library?

Whether you're a library maintainer, contemplating open-sourcing an internal project, or just deeply curious about the architecture that makes modern API testing tick, this is a session you won't want to miss.

Come hear the story, learn from the architecture, and get your questions answered by the person who wrote the code.

In the meantime, you can connect with Robin on LinkedIn.