Tools, Tips and Thoughts for Playwright, Selenium UI and API automated testing
When writing automated tests, assertions are what verify that your application behaves as expected. In most testing frameworks, including Playwright, assertions are hard by default – meaning the test stops immediately when an assertion fails. However there are situations where stopping at the first failure is not ideal. That’s where soft assertions come in. In […]
If you’ve started using Github Copilot to generate Playwright test automation code, boost productivity further by helping Copilot follow your coding style and standards using the copilot-instructions.md file. You’ve probably noticed that while the generated code often works, it doesn’t always follow your project’s conventions and best practice. As a result you may have to […]
Sometimes you don’t want a test to stop immediately an error is found, you want it to carry on performing other related tests. To achieve this in Playwright you can use ‘soft’ assertions. A Typical Scenario: Let’s say you want to verify that a product’s price details are displayed correctly, including the local sales tax. […]
TL;DR : my AI prompt to find missing ‘await’ clauses I am writing asynchronous test automation code using Playwright and Typescript.Check the test code below for missing “await” clauses:test(‘your Playwright test’, async ({ page }) => { // etc…}); The problem – missing an await One of the most frustrating issues test automation engineers can […]
Fixtures are a feature of the Playwright test runner that allows you to define commonly used components or values for your test automation needs. Examples of fixture use include database connections and authentication logic. Playwright fixtures automatically manage lifecycle (setup and cleanup) and can be overridden or customized per test or test file. Playwright comes […]
When writing UI tests with Playwright, selecting the right element is critical for building reliable, readable, and maintainable tests. While there are many ways to locate elements – using CSS selectors, XPath, text content, and so on – Playwright offers a powerful, accessibility-first method: getByRole. This high-level API is part of Playwright’s built-in testing library, […]
Sometimes performing an action opens up a web page in a new browser tab, so how can we handle this in Playwright? TL;DR: with a new Page object. You can see an example of a new browser tab being opened on the Playwright GitHub page in the link to the Playwright developer community website. You […]
Sometimes when writing test automation scripts you come across cases where, after performing an action like clicking on a button, then two different scenarios may occur: for example Page A may load or Page B but you don’t know which. How do you check if the browser has landed on page A or page B? […]
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 […]