Early Bird Savings: 10% off Tickets

Tutorial F

Breaking Down and Improving Your Playwright E2E Tests

Bas Dijkstra

09:00 - 17:00 CEST, Monday 15th June

As part of my day-to-day work, I get to talk to and work with different teams that spend a lot of time writing, running and maintaining end-to-end / full stack tests, and increasingly often, Playwright is their tool of choice. Understandable, because Playwright is a great tool.

However, I also see many of these teams fall into the same two traps when writing their Playwright tests:

* They suffer from long and complex E2E tests being overrepresented in their test suite
* The quality of the code they write leaves plenty of room for improvement

In this workshop, we will address both these traps and improve a Playwright test suite (in TypeScript, prepared by me) by

1. Performing a code review on the test suite, identifying, and discussing potential problems in the code
2. Applying fundamental programming principles and tried and tested automation patterns to improve the readability, maintainability, and extensibility of the code
3. Identify and discuss opportunities to break down the E2E tests into more efficient tests with smaller scope
4. Use Playwright features such as API testing and API mocking to write tests that exercise fewer moving system parts and deliver more valuable feedback, faster

Why do we need these skills in a time where AI can write all of our Playwright code for us, you say? I’m glad you asked!

First, we need the skills required to scrutinize the AI-generated code and see if it is fit for purpose. Deliberate practice like this workshop is a very effective way to grow these skills.

Second, as participants will see, successfully breaking down E2E tests is not just about writing our code differently, it also requires a combination of analyzing product architecture, discussing testability and zooming in on what’s important within a specific context, and these are not exactly topics where AI excels.