WeTest.SKG

When I stepped into the role of a quality coach after working as a Test Lead, I was energized and confident. I had a solid foundation in testing, strong facilitation skills, and a passion for mentoring. I thought I was ready. But the reality turned out to be far more complex than I had anticipated.

Supporting multiple teams as a quality coach introduced me to a whole new level of challenges. I wasn’t just solving testing problems anymore. I was navigating agile dynamics, DevOps hurdles, and organizational expectations that weren’t always clear or aligned. One of the biggest challenges I faced was understanding and clarifying what “better test coverage” actually meant to leadership, and then translating that into meaningful goals for the teams I was coaching.

I quickly realized that coaching isn’t about having all the answers. It’s about asking the right questions, setting the right context, and helping teams prioritize quality in a way that fits their reality. And doing all of that while trying to show visible impact in a short time frame is no small feat.

In this talk, I’ll take you through my journey what worked, what didn’t, and what I wish I had known from the start. I’ll share the tools and techniques I now rely on to guide teams toward building a stronger quality mindset and making meaningful progress. You'll hear how I help teams take ownership of their quality practices in a way that aligns with their goals and context.

As we wrap up, I’ll open the floor to a conversation we all need to have. What does quality coaching look like in the age of AI? The challenges are evolving, and so must we.


Key Takeaways

1) Understand what a quality coach contributes to teams and the broader organization.
2) Uncover the unknown unknowns of quality coaching and learn how to navigate potential pitfalls.
3) Discover tools that can support your quality coaching journey

Automated testing with Selenium can get tricky—especially when dealing with modern, JavaScript-heavy web apps and getting into high amount of tests suite. When total numbers of tests are increasing, it is getting super hard to make a changes in the existing tests and any change can brake number of other tests. Another non-ending challenge in UI testing is knowing exactly when a page (or even just a part of it) is actually ready to be tested. In this talk, I’ll walk you through a practical and proven solution: combining the Loadable Component pattern with the Page Object Model and Domain Dirven Design. This powerful combo not only helps ensure you're interacting with fully loaded pages but also makes your test code more readable and reliable. Based on my experience, I’ll share hands-on strategies, tips, and lessons learned from implementing this approach in complex projects. If you’ve ever faced flaky tests or unpredictable timing issues in Selenium, this session is for you. Join us to learn how to make your test suites smarter, faster, efficient, readable, mentionable and more stable by using. 

Playwright moves fast, and if you blinked, you probably missed a few releases. In this talk, Stefan walks through the features that shipped recently, from smarter debugging and handy utilities to AI-assisted testing, and shows you how they'll change the way you write and maintain your tests.

How do you test an application that relies heavily on cloud services? Do you have a specific strategy for testing it, or do you simply run your tests regardless of the infrastructure costs?


In this talk, we’ll explore how Testcontainers and LocalStack offer an affordable and scalable solution to cloud application testing without compromising on quality. This session will demonstrate (including a live showcase) how to use Testcontainers in combination with LocalStack to spin up containerized services to emulate all the AWS cloud services that your application depends on, enabling you to have your own cloud running locally on your machine or CI/CD. Together, those two tools can provide an efficient, cost-saving alternative to traditional cloud testing strategies.


Here is the agenda that I plan for this talk:


- State of cloud applications nowadays
- What are the challenges when testing cloud applications?
- Which options do we have to avoid some of those costs?
- Introduction to Localstack and Testcontainers
- Localstack and TestContainers in action (live showcase)
- Conclusion


By the end of this session, you will have actionable insights on how to optimize your testing process, lower your infrastructure costs, and ensure your cloud applications are ready for production without complex setups.

AbstractSoftware testing has changed dramatically — but many of our habits, metrics, and assumptions have not. In a world shaped by AI, automation, and intelligent systems, testing is no longer just about finding bugs or executing scripts. Much like quantum physics challenged the deterministic view of the universe, modern software systems challenge the illusion that quality can ever be fully predicted, measured, or controlled.
In this keynote, I rethink software testing through a broader and more human lens — where engineering meets art, logic meets intuition, and automation meets human judgment. Inspired by both quantum thinking and artistic creativity, the session explores why modern testers must move beyond mechanical verification and evolve into interpreters of uncertainty, complexity, risk, and human experience.
Blending real-world stories, provocative insights, AI-era challenges, and parallels from science and art, this session invites the audience to rethink not only software testing — but also the mindset behind quality itself. Because in the end, life is a test — and every human is already a tester.
Key Takeaways

• Why modern software systems behave less like machines — and more like probabilistic ecosystems
• How quantum thinking helps us understand uncertainty, complexity, and non-deterministic behavior in testing
• Why the future of testing requires both engineering discipline and artistic creativity
• How AI and automation are augmenting testers rather than replacing them
• Why quality is ultimately a human, cultural, and business outcome — not just a technical activity