This post is specifically for Playwright Typescript using the Playwright Test Runner. The Playwright team has included a TestInfo class, that includes this information, and a whole lot more! test.describe("/admin", () => { test("login with valid user", async ({ page }, testInfo) => { await page.goto("
A question was recently asked in the Playwright Slack Channel asking if it was possible to click on whichever element was visible out of 2. There was an answer that was provided that allowed me to dive in and learn more about promises in JavaScript. The solution used the Promise.
In the previous article I showed off how to use the playwright-slack-report package to send slack notification from within your Playwright Test run. One of the followup questions people were asking was is it possible to send notifications to Microsoft Teams as well? At the moment this isn't
There are a few ways to tackle this problem I'll start with the easiest solution first in this post which is only for Typescript/Javascript projects. 💡Part 2 to this guide can be found here, which covers sending results to slack via GitHub actions. Playwright-Slack-Report Ryan Rosello has
I recently ran into a scenario where I was attempting to have a Visual Comparison test within a login test, and ran into a slight difference in the way headless and headed versions of chrome handled a scroll bar. * I get a scrollbar from screenshot when running headless: false * I
One of the new page locators that was released with v1.27 was await page.getByTestId("username") makes utilizing custom test attributes easy! Take the example HTML below for a login. In the 3 input fields there is a custom data attribute data-test-id below. <!DOCTYPE html>
💡I've recently updated this as of 11/16/2022! If you've ever run into a situation where you find that you are running your Playwright tests multiple times a day as a GitHub Action, you can save time and money by caching  the downloaded binaries. To
💡These same steps can be used to programatically kick off Github Actions job in any repo regardless of the Test Automation Framework. If you ever find yourself with your Playwright Test Automation code in a separate repository than the service or application under test, have no fear! This post will
Yes it's possible! Deque labs provides a tool called axe to assist with this. For use in playwright they specifically provide the axe-core/playwright package, and getting started is easier than ever. The below code snippet walks through how to use AxeBuilder function from the axe-core/playwright package.
When using the Playwright Test Runner, you have access to test steps, which can be used when reporting steps of certain tests. Here you can define a title to describe the step, and the body which is a function that runs whatever code you want to run during this step.
I know I've run into this issue many times before. It feels like I am in a race to select the element and get a glimpse of the console to actually get the element name. This simple tip may help you keep that drop down or popup visible
If you've ever wondered how to use > or >> in your Playwright Locators look no further. This question was recently asked in the Playwright Slack hi everyone, is there any explanation or article about how should/could I use ">", ">>"