Playwright at Scale

When adopting Playwright, it can be tough to know if you're following the right design principles for a process that will work at scale.
Learn how to implement synthetics monitoring with Checkly at our monthly Kick-Start: us02web.zoom.us/webinar/regis...
For those Cypress users, check out Cypress at Scale. Thu, Jul 11, 2024, 12:00 PM PST: / about
For follow up questions, join the Checkly slack and share in the #Playwright-community channel www.checklyhq.com/slack/
Playwright Discord: / discord
Check out “Improve your Playwright readability with steps” www.checklyhq.com/blog/improv...
Book a Checkly demo: calendly.com/d/5gk-49g-f76/ch...
Filip's first Playwright video • Playwright’s clock API... , Book a meeting with Filip cal.com/filip
Join Jonathan and Filip as we explore how mature organizations and effective teams adopt Playwright. We'll cover what we've seen in the wild and key considerations.
- Fundamentals & principles: You'll understand what Playwright is and its design principles.
- Efficient adoption & migration: You’ll learn how your team can adopt Playwright and move from other testing and automation tools.
- Best Practices: Learn the design patterns you should consider when creating Playwright coverage, including isolation and parallelism, testing methodologies, and advanced use cases
0:00 Introductions
3:30 Agenda
11:35 Playwright supported testing types
16:14 Parallelism in Playwright
23:48 Playwright is an automation solution
32:15 Migrating to Playwright
39:15 Beyond testing: automation with Playwright
44:10 Advanced use cases - handling flake
50:10 Further reading and resources

[@IshwarappaGoudar]

Great Webinar. Very useful !

[@ChecklyHQ]

Glad you think so!

[@alleluiaizimpamvu9971]

Great content buddies, I have started using Playwright and I have integrated in CI, however I have two challenges:
1. It is always a challenge to automate production environment for examples if we have an e-commerce platform ww want to make sure that customers can place the orders seamlessly. How this can be done on production environment since we don't want to record dummy orders on prod.
Note: There is no delete component
2. How to mitigate the failed step or test cases which cause Playwright to skip the all remaining test cases?

[@ChecklyHQ]

Thanks! Happy the webinar has been valuable. 💙
1) This case is a tricky one when there's no delete component. Maybe you could build in a switch in your application without cluttering your DB? But yeah if you want to test end-to-end you have to test end-to-end, so I'd vote for bringing in a deletion component. ;)
2) I'm not sure I understand this. If you're parallelizing your tests they should all be running independently. But if you go for sequential order I think it makes sense that the rest isn't running. It's hard to give guidance without knowing specifics. :)

[@modern_sapien]

Thanks for reaching out here!

[@modern_sapien]

1. Like for any true e2e tests you should have before or after hooks that run some form of cleanup or sanitization when there is a real database involved. This is especially true for when running in production. Your options are; use mocks, intercept requests, or run clean up after or before tests run.

[@modern_sapien]

2. Do you mean that in a given test it doesn't continue after a failure? Or for a spec with multiple tests that once a failure happens none of the other tests are run?

[@alleluiaizimpamvu9971]

@@modern_sapien second scenario you mentioned (spec that has several tests cases in test.describe when one failed remain test cases are skipped