A few weeks back I was approached with a playwright challenge. The challenged seemed like an easy one to solve but I was surprised with the solution, so much so I wanted to share it here and give you a chance to exercise your debug skills. The Challenge 🎯The Challenge:

Good news everyone! This is now possible to do without any external scripts. It is all baked into the Playwright CLI. Original solution If you've been subscribed for some time you may have remembered the original solution. It included getting a list of the file names by running

A Fun Challenge I recently had someone reach out to me with this question. They wanted to run a set of tests with 3 workers and then a separate test run with  with 1 worker and the command looked something like this. npx playwright test --grep-invert @api --workers=3 &

This week our team had a renewed focus on addressing some of our flakey tests, and one of the things we ran across was an interesting page interaction. We wanted to utilize our drop down to limit the amount of responses within a page. The options for filtering  are 5,

I'm a big fan of the Playwright Test Generator when I first start writing tests. I find the tool very useful to quickly identify useful locators/selectors, and quickly generate some test code and assertions from recording my manual actions through a website. Though the code isn'

When a new test automation project starts there are really 3 buckets of work that happen. building (creating new tests), maintaining (updating existing tests as the application changes), and monitoring (keeping an eye on automation runs, investigating failures and surfacing findings to the team). "Flakey" tests really come

Hello Playwright 1.44 release! With this release we now have official support to run failures only from the last playwright run. 💡TLDR; npx playwright test--last-failed Previous Solution Last year I created the json summary reporter and a bash script that can be found in the article below. This was

Do you ever find the need to 🌶️ up your command line interface? Well good news Syzana Bicaj, has released a npm package that allows you to customize your colors but also to indent the spec files in your terminal for easy reading! In order to install the package with the

This past week I was able to participate in a Playwright Ask Me Anything that was hosed by Ministry of Testing. Over the hour we had a plethra of questions that came in that thought would be good to dive deeper on across a few articles. Today I plan to

A few weeks back Ben Fellows created a LinkedIn post asking for solutions around a problem he often faces in his work. As a QA service provider building automation, one challenge I face is allowing the customer to see & engage with the test plan. I've tried TestPad,

The Playwright team just released version 1.40 of Playwright, which included a long awaited feature: the ability to create assertions right from the Codegen tool! This should help lower the barrier to entry for folks new to Playwright making it easier for them to add assertions to their browser

This is the final planned article of this series, where we will discuss Adding CI/CD through GitHub Actions. In this guide I'll walk through the basics of GitHub Actions along with ways you can scale your tests as the suite grows. If you're just joining

There haven't been many times where I wanted to add and validate query parameters on certain requests, but this guide be really useful if you are testing UTM or other types of tracking links that utilize URL parameters. For this article I'll be utilizing the repo

In this guide I'll cover how tags work, link to other articles where I discuss some tips on how to use tags, and show some code examples of the tags I like to use. If you are just now joining us for the first time feel free to

Within my automation tests at work, I found myself running into these two errors within my tests when I use the await page.route() (docs) functionality. Error: apiRequestContext.fetch: Request context disposed Error: apiRequestContext.fetch: Browser has been closed With additional information 1 error was not a part of any

This week I'll be going back and refactoring some tests adding custom assertions to my repo. This is something I considered implementing early on but decided against it, as I wanted to keep things simple. with the release of 1.39 the Playwright team has released some easier

Welcome back, this week we'll look at how to validate the api response body from the schema against the OpenAPI spec schema. This is a more complex solution than we covered in the previous article below. In that article we walked through taking a snapshot of the response,

Ok so I will admit, I was tempted to title thisBest Practices but decided to stick with Great practices because all the advice I plan to give really "Depends on Your Context". I do however plan to give you some good advice along with rationale so you can

In part 11 of this series I will cover how you can add multi environment support to your Playwright project. There are multiple ways to handle this depending on how you have built your project. I'll cover the way I handled it which includes having different .env files

Welcome back! In this weeks guide I'm going walk you through the a pull request that was made by a reader Adam Pajda. He took some time and added unit tests around 4 different functions that I created through this series. For this article I will walk through

This is a very popular question that gets asked quite often in the Playwright Discord help channel. One of the main reasons I believe this is so popular is because no one wants to write the same code over and over for the same operation with a slightly different input.

This was a recent question that was asked in the Playwright Discord channel. I want to do some kind of "reset" in a specific table after every spec. I could simply achieve it by setting up an afterAll in each spec but this is equal repeating the same

Welcome back! In this weeks guide I'm going walk you through the tooling I use to help me create JSON schema snapshots, and asserting on those snapshots within Playwright API tests. If you're just joining us now go check out the introduction post which links to

I'm a big fan of consistency within a codebase. I somewhat care less about the specifics as long as it's the same. Today I'll cover extra tooling that are common in the JS/TS ecosystem to help solve common errors and consistency. If you&