One More Technique to Avoid Timeouts as Fix of Flaky Tests
Andrey Enin offers useful advice on reducing web UI test flakiness by waiting for API calls to complete before taking action in the test.
Moreover, Irfan Mujagić describes Handling Caching in Automation Testing that can help with cleaning state before running consequent tests.
How to make your GUI test automation less flaky and brittle
And if you're hungry for more test automation improvement tips, here comes Kevin Tuck with a solid piece of advice on making your UI tests more stable.
Test Flakiness — One of the main challenges of automated testing
Here's a good read from George Pirocanac on where test flakiness comes from in distributed services and what the potential remedy is. I'm looking forward to reading the next part on how to overcome those challenges.
Mastering the Art of Detecting and Handling Flaky Tests in Playwright
Facing unstable Playwright tests? Luc Gagan wrote a super detailed guide with many examples and scenarios on how to analyse, find, and fix them.
It may also help to Test multiple environments locally in Playwright with .env file, as Thara Perera suggests.
And once you have that steady pipeline, Pirasanth Jesugeevegan shows how to Create a Jira issue when a test run fails using Playwright.
What causes end-to-end flakiness and how to address it
Flakiness is a common problem in test automation. Marcin Wosinek explains where it comes from and how you can improve it in your projects.
Furthermore, Jérémie Fleurant shares insights into How I Managed to Leave My E2E Tests for Months and Find Them All Green.
Finally, you may also want to Use your own click() method to make your test automation more robust and reliable.
From Fragile to Agile: Automating the fight against Flaky Tests @ Reddit
Curious how Reddit tackled its flaky tests? Kudos to Abinodh Thomas for sharing this comprehensive overview.
Enhancing Test Stability With Test Doubles for Flaky Test Management
Marvel Ken-Anele gives examples of all types of test doubles — such as mocks, stubs, fakes, and more — that can be used to make your tests more stable.
You may also want to read Shubham Sharma's guide on The Easiest Way to Identify Flaky Tests in Jest.
Why you shouldn't run tests sequentially
Writing tests that rely on execution order may lead to test flakiness. Nočnica Mellifera explores better alternatives like fixtures, hooks, and test steps.
Also, Lana Begunova advises to Stop Running High-Risk E2E Tests in Every Browser.
Stop the Retries in Tests & Reruns of Failing Tests
What I liked about Anand Bagmar's article is not only that it shows why flakiness is an issue that shouldn't be solved by frequently used test retries (which are built into most test runners) but also provides some really helpful pieces of advice on how to track down the real causes.
