I found my way into IT engineering in 2014, right after finishing compulsory school. After a four-year apprenticeship at Swiss Post, I jumped straight into the heart of PostFinance: the acquiring system, where all card information is processed up front.
During my two years with that team, I laid a major milestone for my current work: faced with quality concerns, I introduced the Citrus framework to PostFinance. After switching teams twice - and studying IT engineering along the way - I returned to a dedicated test automation team. That team took my early experiments with Citrus and turned them into a professional foundation.
Since then, I’ve learned a lot - on the job and in my spare time. I’ve programmed a lot (yes, I’m quite the nerd), and together with my team, we’ve pushed things further: improving not just the quality of our test tooling, but also its adoption across the company. We’ve designed tools, workflows, and even helped define a company-wide “delivery pipeline goal.” Turning a Swiss bank into a digital powerhouse isn’t easy - going from two releases per year to continuous delivery is a challenge. But it’s one we’re taking on.
I’ve been serving as Architecture Owner for Test Automation for three years now, and I don’t see that passion fading anytime soon. It’s a huge, fascinating field - and I feel like I’m just getting started.
Oh, and by the way - I do have a private life. Luckily, in Switzerland, the mountains are never far. You might even find me reviewing a pull request from a Swiss Alpine Club hut 😉
In this fast-paced tooling session, I'll show you how the Citrus Framework and Citrus Simulator can take your OpenAPI-based testing to the next level. Within the juicy 25-minute mark, I'll demonstrate how to generate Citrus actions from an OpenAPI specification. These actions can be used to test your system under test (SUT) in a black-box scenario. On the flip side, we'll use the same specification to create simulations of third-party systems - allowing you to isolate your SUT with confidence.
We'll cover how to:
- Generate test clients directly from your OpenAPI spec
- Build simulations that return realistic, randomized data
- Automatically validate schema conformity on both the client and simulation sides
This setup not only improves test quality but also enhances collaboration between teams. Issues can be caught early in the specification phase, and by the time integration arrives, much of it has already been tested. It's also a promising first step toward contract testing with tools like Pact.
At PostFinance, one of Switzerland's leading banking companies, we use the Citrus Framework with OpenAPI testing every day to ensure seamless continuous integration across our services.
Searching for speaker images...