Someone on Reddit is wondering what makes people use full-code over low-code solutions to write automated tests. There are some interesting answers.
The Browser Automation Newbie Experience
Maaret Pyhäjärvi shares learnings from using Playwright and Selenium to automate web app tests with newbies.
Request-Mocking-Protocol: A New Approach to Mocking Server-Side Requests in E2E Testing
In this detailed overview, Vitaliy Potapov proposes a scalable, proxy-free method for mocking server-side API requests in Playwright tests in order to improve their reliability.
A brief introduction to Accessibility Testing using Axe
If you want to learn how to automate accessibility tests for your website, Ajitava Deb wrote a helpful guide on integrating Axe with Selenium tests in Python.
Similarly, Sean Coughlin explains how to implement them using Playwright and Axe-Playwright.
How To Use Playwright's testInfo.retry To Deal With Flakey Environments
We've had some Cypress tips, now it's time for Playwright. Here's a helpful one by Sergei Gapanovich about smarter test retries.
Furthermore, Irfan Mujagić explains how to Handle Unreliable API Endpoints with Custom Retry Logic and Mocking with Playwright.
Unlocking Playwright's Potential: Features for daily basis
Kostiantyn Teltov shares lots of tips for Playwright tests, explaining each one with helpful examples.
Similarly, Rajesh Sharma wrote about Boosting Testing Efficiency with Playwright: Simple and Effective Tips.
Jan Molak, one of Serenity/JS creators, created templates for using this handy framework with Playwright and WebdriverIO.
Comparing Top AI Models for Test Failure Analysis: Which Performs Best?
AI enables us to get more insights from test reports. Matthew Poulton-White tested out a few models and shared the results.
Similarly, Razvan Vancea explored AI-powered Playwright Test Reporting with Testbeats, followed by Thananjayan Rajasekaran demonstrating the well-known Report Portal with Playwright.
Here's great advice from Tim Nolet on why it's so important to avoid hard waits and rely on a smarter approach instead. It also includes examples using Puppeteer and Playwright tools.
Similarly, Sajitha Pathirana explains why not to use hard assertions everywhere.
Welcome to the 275th issue!
The extensive Software Testing and Quality Report (4th Edition) from TestRail is out.
Among many insights, I found these to be the most interesting:
You can also read two write-ups here and here.
Happy testing! 🙂
