Michał Krzyżanowski

Having your own test automation framework is something natural for an established, serious and self-respecting company. Of course, you get additional bonus points when you make such a tool public as open-source. 

Very often though, we do not pay enough attention to the consequences of decisions like that. Pushing code to GitHub is as easy as few clicks, but we do not have a roadmap or an idea of how we will actually support the growth of our new product.

I would like to tell you what I have learned about:

– designing an API that serves a wider audience, 

– supporting community,

– managing documentation,

– consequences of decisions that made perfect sense back then (or you thought of it as the best idea you ever had)

– why is it worth to go open-source anyway

and other things I have encountered when taking care of my company’s open-source framework, Bobcat.