Here at Wrobocon, we believe that the heart of any great conference is its speakers. These are the folks from the trenches, the ones who've seen it all and have the battle scars (and hopefully, the solutions) to prove it. Today, we're shining a spotlight on one such individual: Kacper Borucki.
From Reliable Hardware to Buggy Django
Kacper is a Pythonista who has ventured deep into the world of networking, working with giants like Nokia and now, BT. He spent his time at Nokia on a noble quest: making smoke tests for hardware reliable. This involved wrangling internal Python libraries, restructuring tests, and creating enough documentation to build a small library. We've heard it said that if you want to understand something, try explaining it to someone else. Kacper apparently decided to explain it to everyone.
Now at BT, he's tackling a different kind of beast: a Django project that has proven to be... well, let's just say it has character. While not always in the driver's seat for the Robot Framework E2E tests, he's often the one in the passenger seat, helpfully pointing out things the driver might have missed during code reviews. It seems once you get a knack for simplifying Python and automating tasks, it's hard to turn it off.
When he's not untangling code, Kacper enjoys reading books, hitting the gym, traveling, and writing. A man of many talents, and we're glad he's sharing some of them with us.
Testing Your Tests: A Paradox?
Complexity is the enemy of reliability. As our Robot Framework projects grow, they can become unwieldy, and suddenly, the tests that were meant to bring peace of mind are causing the headaches.
That brings us to Kacper's talk: "Robot Framework + PyTest, or why you should test your tests."
Is it possible our tests have become so complex they need their own tests? When is it time to step back from Robot Framework and let unit-tested Python take the wheel? Kacper will explore the intriguing intersection of Robot Framework and PyTest, offering insights that might just save your next big project. If you've ever looked at a failing test and wondered if the problem was the code or the test itself, this is a talk you won't want to miss.
Join us at Wrobocon to hear Kacper dive into this fascinating topic.
