2022-05-20 –, Main Hall
So you created your own Library for Robot Framework and use it in your internal projects. And then you remember - sharing is caring :)
But how to release it?
What do you need to set up?
How to package and test it?
How to create the documentation?
I faced that challenge not so long ago and would like to help you getting started.
It happens quicker than you think. You face a Test Automation challenge and realize that you cannot solve it using existing libraries. So you develop your own.
Then you remember: Open Source is about sharing. Maybe this library can also help other people? But you have no idea how to release it to the public. Executing a 'pip install <your-library>' seems lightyears away.
When I released my first library last year, I was worried about making a fool of myself when I released it. Worried about not following the correct standards and doing it all wrong. I found many approaches on how to package libraries.
Which one shall I choose? How can I release things easily? Did I test the library properly? How to document it? And what if something goes wrong?
Let me tell you one thing: Releasing anything is better than releasing nothing. But it requires courage to put something out there in the open. You need to find that courage yourself. But I want to give you confidence by setting up a basic approach and structure that you can follow to test and release easily. So that you can focus on the implementation, instead of spending too much time on research for your project setup.
In this talk we’ll create our own project structure for a Robot Framework Library on GitHub.
We’ll talk about Python packages, dependencies, static & dynamic libraries, Unit & Acceptance Tests, documentation and more.
We’ll use GitHub Actions to run our tests, publish to PyPi and generate the Keyword documentation to be stored as GitHub Pages.
I'm a Test Manager at DB Schenker and a regular Robot Framework User since 2020.
I like to help other people getting started with Robot Framework (and Test Automation in general) and I know that it can be overwhelming sometimes.
In my daily work, I support projects in the setup of their test automation solution - for Web Applications, Desktop Applications, APIs or even Document Tests.
I'm a believer in test automation - but convinced that testing itself cannot be automated.