Tools, Tips and Thoughts for Playwright, Selenium UI and API automated testing
Sometimes when you’re writing a test you’ll find you want to run the same test multiple times, but with different data. For example let’s say you need tests for a UK e-commerce website to verify that the correct sales tax (VAT) is applied to purchases. Most products in the UK incur VAT of 20% but […]
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 […]
Test automation engineers frequently inspect web elements using the “Elements” tab of a browser’s Dev Tools like Chrome DevTools to discover the ID or other attributes needed to locate them in their test scripts. However many modern frameworks like React can make this difficult because the elements can disappear when the mouse moves into the […]
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 […]