Welcome to the 301st issue!

Two years ago, we learned how Reddit approaches the eternal fight with flaky tests.

Today, I'm happy to share with you the second part of that journey, delivered by Abinodh Thomas:

From Fragile to Agile Part II: The Sequence-based Dynamic Test Quarantine System.

There's some good inspiration there.

Happy testing! 🙂

Dawid Dylowicz

I regularly see people asking about switching between dev and QA, and this thread offers some good insights into what it takes.

And it's not only me — John Caleb Pananganan has also noticed this trend of Developers Wanting to Move to QA, and QA Wanting to Move to Development, including the follow-up second part.

Is our profession really stuck? Katja Obring makes a few good points on why we should share and apply our testing knowledge, especially now.

Similarly, Amalie Shi shares interesting thoughts after attending a webinar about How to Coexist with AI as a Tester.

If you want to improve your QA processes, Viviane Hennecke and Ralf Kleinhietpass share their approach focused on putting people first, adjusting roles and leveraging AI for support.

Similarly, Tamar Baratashvili has a few solid points on how Testers Help Products Become What They Were Meant to Be.

I really like this statement by Elizabeth Zagroba. As a vision, that's what we should aim for.

Furthermore, Michael Tomara wonders about Calculating the QA: Not So Simple in search for the perfect dev-to-QA ratio.

How do you keep quality when AI builds most of the software? Yanir Taflev reflects on changing responsibilities of testers to keep adding value.

Moreover, Rodrigo Alves Costa brings up an important point on Why Manual Testing is More Relevant in the Age of AI.

In order to enable collaboration between testers, Muhammad Ahyar Ibrahim Aldebaran came up with a way of handling tests per environment using sandbox, staging and master branches.

Vera Marczenko gives plenty of practical advice on how to improve the "arrange" part in tests. It's followed by another article about AI-Generated Test Data: Powerful, Dangerous, or Both?.

Bold claim, Antony Fuentes! But as the saying goes, there might be a method to this madness, as explained here in detail.

Suryakanta Mohapatra shares a technical deep dive into how they achieved auto-locator healing using the all-MiniLM-L6-v2 sentence transformer model.

Rajesh Yemul continues a great series of articles showing practical code examples to create a full-fledged test automation framework with Playwright. This part focuses on assertions.

Moreover, Sajith Dilshan shows a few tricks to speed up Playwright tests by Mastering Non-Linear Execution with Async/Await Patterns.

Kulanthaivelu Sankaran describes a handy, open-source AI agent solution for generating tests using natural language commands called Checkmate.

If you're looking to improve your Cypress tests, Sebastian Clavijo Suero demonstrates commands that can help you handle async patterns.

Mohammad Faisal Khatri created a comprehensive, step-by-step guide to setting up an API test framework with REST-assured. You can access the following part 2, part 3 and part 4.

Testing LLMs? Irfan Mujagić gives a nice overview of how to achieve that with Promptfoo.

Similarly, Meryem Sakin has also written a good article about Testing AI Agents in CI Pipelines (Promptfoo + Golden Traces).

This might be helpful to many of you looking to use AI to aid test automation. Alex Khvastovich recorded an 18-minute overview demonstrating his setup.

Some bugs be like... 😂

Thanks for reading!

If you enjoy this newsletter and find it helpful in becoming a better tester, please consider sharing it with others.

Dawid Dylowicz