Tools, Tips and Thoughts for Playwright, Selenium UI and API automated testing
Most of the time when you want to check an element is visible in Playwright you do so as part of a test assertion. For example if you’re testing that attempting to log in using an invalid password displays an error message, your test might look something like this: This is absolutely fine because checking […]
Sometimes you create a Playwright test but can’t seem to actually run it in Visual Studio Code. Here are the most common reasons why, and how to fix it. Incorrect File Name Playwright uses certain conventions to identify test files. Depending on the language you’re using, ensure that your test files end with: Playwright Test […]
Are you getting an error when trying to execute commands in the Visual Studio Code terminal window, with the error message containing the text “{executable file} is not digitally signed”? For example when running “yarn dev” I get this error message: Here’s the actual screenshot: One way to fix this is to run this code […]
Many test automation frameworks like Playwright support the use of a data-testid attribute (or similar) as a method for locating elements on a web page. For example we can locate this element: and populate it with some text using this Playwright code: Although data-testid is the most common name for this attribute – which is […]
Playwright has become the test automation framework of choice for many software development teams for good reason. In this article we’ll look at the main advantages – and disadvantages – of using Playwright in the real world. Advantages of Playwright 1) Automatic Waits One of the biggest problems with test automation is flaky tests, and […]