Days
Exclusive Talks & Hands-on Workshops
Live Panel Discussion
Networking
Why you should go?
Experience the vibrant atmosphere of Tesena Fest for yourself! By attending, you will have the opportunity to connect with experts, gain insights from real-world cases, share your experiences, and be inspired by fellow attendees. Elevate your skills, stay ahead of trends and expand your professional network. Do not miss out on the chance to enrich your knowledge and engage with the testing community at Tesena Fest!
What do we want to talk about?
- Quality Engineering
- Agile
- Artificial Intelligence (AI)
- Testing
- Test Automation
- Accessibility
- Working in Teams and Leadership
- DevOps
Event for:
- Quality Engineers
- Business Analytics
- Business Consultants
- Testers
- IT Managers
- Project Managers
- Technical Leads
- And everyone else who is interested in the world of testing!
24. 9. 2026
Workshop and Conference Day
We are preparing 4 exclusive workshops for you to choose from:
AI-assisted API Testing with Claude Code and Superpowers
| Lucie Lavičková
How Leaders Can Help Transform QA Roles into True Quality Partners
| Lucie Paulíčková & Phil Royston
Vibe Testing Lab: AI Agents, MCP, and the New Stack for Web App Testing
| Marcel Veselka & Jan Beránek
Quality Engineering: How to Overcome the Struggle for Quality at Speed
| David Sedláček & Katarína Vavreková
*Workshop Day will take place at Holiday Inn Prague.
*This Workshop Day ticket includes admission to the Conference Day.
*All ticket prices are listed excluding VAT.
Buy ticket now
10.590 Kč / 435 EUR
25. 9. 2026
Conference Day
What awaits you at the conference?
- Inspirational Presentations
- Expert Insights
- Networking
- All-Day Complimentary Refreshments
- Afterparty
*Conference Day will take place at Cubex Centre Prague.
*All ticket prices are listed excluding VAT
Buy ticket now
6.900 Kč / 285 EUR5.500 Kč / 224 EURProgram
About the Workshop
As release cycles get shorter, teams need test feedback they can trust quickly. GUI tests are valuable, but expensive. For many scenarios, API tests give better speed, lower cost, and more stable execution - which makes them a strong foundation for CI/CD feedback.
In this hands-on workshop, we’ll use Claude Code and Superpowers to build a practical API testing workflow. We’ll start from a GitHub issue, let an AI coding agent inspect the API documentation and existing tests, then generate or update automated API tests. You’ll also try how AI can help with work that usually takes time: finding missing coverage, reviewing API contracts, and analysing failed pipeline runs from logs and test artifacts.
The goal is not to replace your testing skills. The goal is to show how AI can handle part of the repetitive work, while you stay in control of the design, review, and final decision.
What You’ll Learn
- How to use Claude Code for API testing tasks
- How to write GitHub issues that agents can work with
- How to generate and review API tests from OpenAPI (or any other) documentation
- How to find missing API test coverage
- How to analyze failed API tests from CI logs and artifacts
- How to use Superpowers for repeatable testing workflows
Walk Away With
- A working AI-assisted API testing workflow
- Example GitHub issues for agent-based test automation
- Reusable Superpower templates for API testing
- A practical failure analysis workflow for broken API tests in CI
Who Is This For?
QA engineers, test automation engineers, developers, and anyone working with API testing.
You don’t need to be an AI expert. But basic experience with APIs, Git, and automated tests will help.
What You’ll Need
Please bring your own laptop. You’ll also need:
- a GitHub account
- Git installed
- Node.js LTS installed
- a code editor, ideally VS Code
- ideally your own Claude Code access
If you don’t have a Claude Code licence, don’t worry - we’ll have a backup setup ready, so you’ll still be able to participate.
About the Workshop
Many quality challenges today are not technical - they stem from misalignment, unclear ownership, and ineffective communication. Leaders play a key role in shaping how quality is perceived and practiced within teams.
This workshop explores how leaders can transform QA roles into true Quality Partners who work closely with product, engineering, and business stakeholders to proactively influence quality throughout the development lifecycle. Through interactive exercises and peer discussions, participants will learn how to create the conditions, communication practices, and team dynamics that enable quality to become a shared responsibility rather than a final checkpoint.
Who is this workshop intended for?
This workshop is designed for leaders and managers who influence how quality is organized, communicated, and supported within their teams or organizations, including:
- Test Managers and QA Leads
- Engineering Managers
- Product Managers and Product Owners
- Delivery Managers and Project Managers
- Heads of QA / Heads of Engineering
It is especially relevant for those who want to move beyond traditional testing models and enable stronger collaboration and ownership of quality across teams.
Key Topics
- Gatekeeper vs. Quality Partner. How to take the first step toward a paradigm shift?
- Prevent misunderstandings. How to communicate with others and make yourself heard.
- Team collaboration and communication. We will play a fun game!
- Team chemistry. How to build (and let go of) a great cross-functional team.
- The importance of feedback. Feedback as a cornerstone of everything.
- Influence without authority. Testing typically walks a fine line. How do we get out of this?
Why join?
This workshop provides a practical space to reflect on your current approach, learn from others, and explore how to create an environment where quality is built in, not inspected at the end.
If you want your teams to move beyond testing as a checkpoint and become true partners in delivering quality, this workshop will give you the tools and perspective to make that shift.
| Format | Full-day hands-on workshop |
| Language | English |
| Facilitators | Marcel Veselka & Jan Beránek, Wopee.io |
| Audience | Test automation engineers, QA leads & managers |
| Prerequisites | Basic Playwright or Cypress experience. No AI/LLM background required. |
| Bring | A laptop. Leave your comfort zone in the parking lot. |
Do you think you know test automation. You wrote the scripts. You fixed the locators. You survived the flaky pipelines. You thought you were fast.
You had no idea.
This is not a workshop about what AI might do to testing. This is a workshop about what it is already doing and why your current setup is about to look like a Honda Civic at a drag race.
We go full throttle from minute one. Playwright. Playwright CLI. Playwright MCP. Wopee.io. AI coding agents writing your tests while you watch. AI testing agents running them while you sleep. API testing that does not wait for anyone.
Same app. Different tools. Head-to-head. You pick the winner.
Some tools will surprise you. Some will disappoint you. One will make you question every afternoon you spent chasing broken selectors. That moment. That specific moment. It is why you are here.
By the end of the day you will have built something real, broken something on purpose, and learned more about the new testing stack in eight hours than most teams figure out in a year.
What you will do
- Run Playwright the traditional way, then via CLI, then via MCP and see exactly what changes at each step
- Experiment with Wopee.io as a purpose-built AI testing agent on the same app, same task direct comparison.
- Wire an AI coding agent to generate, run, and interpret tests autonomously
- Write a SKILL.md that encodes your team’s testing knowledge so any agent can reuse it
- Get hands-on with AI-assisted API testing. Same agent concepts, one layer below the UI
- Build a working test suite your team can actually use next week
What you will walk away with
- First-hand experience with the tools shaping web app testing in 2026
- A working AI-assisted test suite you built yourself
- A SKILL.md your agent can run cold, without handholding
- A clear answer to the question your team keeps asking: where do we actually start?
How the day runs: No death by slides. The day has 4 gears.
- The Zoo: 4 exhibits. Same demo app. Playwright CLI, Playwright MCP, an AI coding agent, and Wopee.io. One at a time, side by side. Every tool gets the same fair test.
- Teams and mission: Before lunch you get assigned to a team and handed a mission card. Lunch is yours. But your team is already talking.
- Build 1 thing: 90 minutes to build a real AI-assisted test suite. Including a reusable capability your agent can run cold, without guidance. This is the thing you take home.
- Speed gap battle: 3 new features just shipped on the demo app. Your suite is your only weapon. 45 minutes. Maximum coverage wins.
Not a fit for you if…
You have never written an automated test before. This workshop moves fast and assumes basic Playwright or Cypress experience.
You are looking for a vendor comparison or a product demo. Every tool gets the same fair treatment. Including the ones we built.
About the Workshop
This updated version of our workshop shifts the focus more firmly toward practical quality engineering skills you can apply immediately. While the core idea remains the same - building quality into your process rather than testing it at the end - we now place greater emphasis on hands-on exercises and real-world application.
You’ll work through a series of focused activities designed to reflect common delivery challenges: balancing speed and quality, working within constraints, improving flow, and making better engineering decisions under pressure. Short theory inputs will frame each topic, but most of the day is dedicated to practice, discussion, and applying ideas to realistic scenarios.
Because every group moves at a different pace, the exact mix of topics will adapt during the day. This allows us to go deeper where it matters most, rather than covering everything superficially.
What to Expect
A dynamic, exercise-driven workshop combining:
- Short, targeted theory segments to introduce key concepts
- Practical group exercises focused on real delivery problems
- Facilitated discussions to connect ideas to your own context
You’ll explore how to:
- Improve flow and reduce inefficiencies in your process
- Identify and manage quality risks early
- Apply modern engineering practices that support quality at speed
- Strengthen team collaboration around quality
Three Things You’ll Take Away:
Practical Quality Engineering Skills
Techniques you can start using immediately in your team - not just theory.
Better Decision-Making Under Constraints
How to balance speed, risk, and quality in real delivery situations.
A Clearer Path to Building Quality In
Concrete ideas for evolving your current approach toward quality engineering.
Why This Workshop?
You won’t just talk about quality - you’ll think about quality differently. You'll leave with the experience and approaches that you can start applying in your own team and environment.
I asked an AI assistant to help me with a database query. The code came back clean. Well-structured. It passed my first review. It also had a vulnerability that could have exposed our entire user database.
My first reaction wasn't, 'Let me check this carefully.' It was, 'This looks really good.'
That's the problem. AI doesn't fail the way we expect. It produces confident, well-formatted, professional-looking mistakes. Code that compiles. Code that reads like a senior dev wrote it. And we're approving it.
This session is an interactive detective hunt for testers, QA engineers, and anyone reviewing or approving AI-generated code. AI-generated examples appear on screen. You try to spot what's wrong before the reveal. Multiple rounds. Each one harder than the last. And one of them will surprise you.
Along the way we'll name the cognitive traps that make this so hard. I've fallen for all three. Chances are, you have too.
You'll leave with:
- A starting point for building better habits around AI code review
- A way to think about AI output that goes beyond 'does it look right'
Speaker
Martin Matejovič
Senior iOS Engineer at Spotify
Speaker
Martin Čambal
AI Program Owner and Senior Global Web Development Manager at ESET
Speaker
Juraj Žabka
Head of Technology at Multitude IT Labs
Speaker
Marcel Veselka
Founder | Wopee.io and Tesena
AI is changing how software gets built, but the real story is happening behind the scenes. As teams experiment, adapt, and rethink their workflows, not everything lives up to the promise.
This panel brings together a mix of engineering and leadership perspectives from top companies, offering a grounded view on what actually holds up across the software lifecycle from development to testing to delivery. Beyond the AI hype, it reflects real-world experience, trade-offs, and lessons learned under pressure.
Because the real question isn’t just what AI changes, but what else is quietly redefining how software gets built today.
99.59%.
That’s not uptime, not coverage - it’s our yearly stability rate of mobile end-to-end test runs. Almost perfect. Almost unbelievable. Especially after three years of endless debugging, failing builds, and a growing Slack thread titled #iHateMobile.
This talk is a story - but also a survival guide - for anyone who’s ever wanted to throw their test phone across the room. It’s about turning unreliable, flaky chaos into a system that’s fast, predictable, and trusted by developers and managers alike.
We’ll start where it hurts:
Phase 1 – The chaos. Appium and WebdriverIO giving us nightmares - element interaction timeouts, deep-layer selectors that vanish, “TouchableOpacity” not being so touchable. The usual suspects, multiplied by hundreds of test cases and dozens of devices. I’ll show how we diagnosed the real causes of instability and how small framework-level fixes snowballed into huge stability gains.
Then comes phase 2 - the great optimization. Once the framework stopped screaming, we focused on speed and cost. Data seeding through APIs instead of UI clicks. Custom app states and DB shortcuts. And our proudest creation - a homemade device-thread balancer that decides how many tests to run, where, and when, saving both time and money.
Next up, phase 3 - testops and devops join the party. We automated everything around testing: app building, downloading, device-farm uploads, CI triggers, even tagging pull requests to auto-launch tests. It’s where manual setup finally died, and “one-click testing” was born.
Finally, phase 4 - flexibility and trust. We added real-world smarts: handling conditional popups, feature flags, experiments, and 2FA flows that used to break everything. This turned our test suite from a rigid framework into something dynamic - something that works with the product, not against it.
And because tools alone don’t fix culture, the last part is about people - the skeptics who thought E2E testing was a waste, the processes that slowly built trust, and the moment when “just run it” became the team’s favorite phrase.
If you’ve ever struggled with flaky mobile tests, this talk will show you that the pain can end - with patience, curiosity, and a few clever hacks. You’ll leave with real techniques, architecture ideas, and maybe even the motivation to start your own “painful but worth it” journey toward outstanding stability.
1. Introduction to the case
A quick look at where we started, what stability really means in mobile E2E testing, and why it was such a painful problem to solve.
2. Phase 1: The chaos
Early challenges with Appium and WebdriverIO, the most common sources of flakiness, and how we started fighting back.
3. Phase 2: The great optimization
Speeding things up and cutting costs with smarter data handling, app state setup, and device management.
4. Phase 3: TestOps and DevOps join the party
Automating everything around testing, including builds, uploads, and CI triggers, and finally reaching the dream of one-click testing.
5. Phase 4: Flexibility and trust
Making the framework adaptive and reliable while building trust with developers and product teams.
6. Wrap-up
Key lessons, mistakes, and mindset shifts that turned chaos into confidence, and how others can follow the same path.
Key learnings:
- Root Cause Analysis: Techniques for diagnosing the real source of mobile flakiness (it's not always the device).
- Speed vs. Stability: How to use API seeding and backend shortcuts to stabilize frontend tests.
- DevOps Integration: Blueprints for a 'device-thread balancer' that optimizes cost and speed.
Culture: How to build trust with developers so they treat E2E tests as an asset, not a blocker.
Speakers
Christine Pinto
QA Leader
Dawid Pacia
QA & Test Automation Manager
Martin Matejovič
Senior iOS Engineer at Spotify
Martin Čambal
AI Program Owner and Senior Global Web Development Manager at ESET
Juraj Žabka
Head of Technology at Multitude IT Labs
Marcel Veselka
Founder | Wopee.io and Tesena
Partners
Become a partner
Join us at Tesena Fest 2026 as a valued partner and align your brand with the forefront of software testing innovation. In the heart of Prague, this intimate yet dynamic conference provides a unique platform for sponsors to engage directly with around 350 passionate professionals from the testing and IT sectors. We offer tailored sponsorship packages designed to showcase your services and products, amplify your brand, and foster meaningful connections. Let's collaborate to make an impact and drive the future of quality assurance together.
Curious about past editions of Tesena Fest?
Tickets to Tesena Fest 2026
Don't miss out on the latest updates.
Fill in your email address to stay informed about upcoming training sessions, events, and testing know-how.