Have you ever struggled to run specific tests from the command line? I've had the want to run 2-3 tests from the command line together and struggled to autocomplete my way through building the proper command manually. With this new tool I don't have to craft
With the latest 1.50 Playwright release, there was a really nice feature that was released that will help speed up test automation api requests. The feature is found on the Playwright Trace Viewer which is found in Playwright UI mode or the HTML test report. From Playwright Test Report
If you've ever been in a scenario where a test you were writing changed the state of the system or user in a way where other tests would fail? This solution may help you. While I am a big fan of running my tests at the same time
I wanted to share a few exciting announcements here and via the newsletter! 1. I'm a Linked In Learning Instructor. At the end of November the "Learning Playwright" Course that I've been working on the last few months was released. I've been
This week I'll walk through a Playwright Test with 2FA enabled. 2FA or Two Factor Authentication is a common recommended security measure to protect users accounts across the internet. Having a way to test this functionality in your CI/CD pipelines within your Playwright tests can ensure that
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'
The environment I am working with can be unstable sometimes. To ensure I don't have false negative tests, I need to rerun the failed checks. Playwright makes this easy by allowing you to pass --retries followed by the number of retries. Skipping certain tests if retried The problem
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