Welcome to the 290th issue!

How is AI changing testing?

Some say it's only a helpful addition to our work, while others claim it may replace the majority of our responsibilities.

I enjoy learning different points of view, and today I want to share with you several opinions that I've found recently:

• AI-Driven Software Testing Trends 2025 by Ryan Craven
• Why Only 10% of Testers Will Remain by 2030 by George Ukkuru
• When AI's "Perfection" Becomes the New Bug by Maksym Kombarov

Happy testing! 🙂

Dawid Dylowicz

Tracking testing across releases isn't easy, especially when information is spread across different tools and channels. Marina Jordão describes how they automated that process based on the Jira status and suggests how AI can help further.

Similarly, Sudeep Patra considers using The QA Assistant Trained on Bug Backlog to help with triaging.

This is a great, thought-provoking article by Vernon Richards about why DORA metrics might not be perfect and an alternative approach to metrics.

Furthermore, Veronika Moran shares how they implemented QA metrics from scratch and Abhishek Verma gives practical advice on How I Use Data Analytics to Find Gaps in Test Coverage.

Mona M. Abd El-Rahman takes us on an interesting journey, describing in detail how Quality Engineering was born and what practices it involves.

Furthermore, Pritanshu Dwivedi says that Quality Is Everyone's Job — Thanks to the Platform Team that helps put the structure in place.

When it comes to testing, we often find ourselves in imperfect environments, with some information missing here and there. Charlie Kingston comes up with an analogy to explain how good testing practices can help.

Similarly, Mark Nicoll offers guidance on Working With No Requirements.

Interested in running performance tests? Yanming Zhai gives a few helpful tips on how to prepare well for that, regardless of the tools you're planning to use.

Similarly, Alireza Ghorbani explains why it's good to take into account The Truth About "Simultaneous" Requests in Load Testing.

Whether you're a tester or developer, debugging will inevitably be part of your job. Hanisha Arora gives several concise tips for doing it well.

In relation to that, Maaret Pyhäjärvi explains why it's important to focus on Feedback and Actions as testers.

Someone shared their problem with flaky automated tests and asked for advice. There's been a lot of insightful responses from the community on how to address this specific problem, as well as test flakiness in general.

And, in another discussion, someone points out why Structural XPath locators are killing your test stability (and what to do about it).

Continuing the series on setting up a test framework for a web application, this time Dmitry Ivanov demonstrates how to implement Cypress end-to-end tests running in the GitHub Actions pipeline.

Furthermore, Mrinal Maheshwari gives an overview of How to Write Unit Test Cases for Any Application.

It's a good practice, but only when done right. It requires a strong culture and preparation, as outlined by Deepesh Mohan.

Similarly, Kiryl Dubarenka describes Why Good Engineers Skip QA if there's a high confidence, which means going beyond just testing in production.

Nearly every web application requires some sort of authentication to test most flows. Vitaliy Potapov shows some smart features to achieve that in Playwright.

Anyone who has tested mobile apps knows that getting the right locators can be tricky at times. Saeed Roshan demonstrates FunnelPeek — an open-source UI inspector for Android to find paths more easily.

What's more, Josphine Job shares a story of How We Fixed Android WebView Automation in Appium 2.

Playwright definitely stirred up excitement with their recent release of natively supported test agents. Kostiantyn Teltov gives a detailed overview.

Moreover, Eleonora Belova shows an in-depth example of applying Model-Based Testing with Playwright.

Cypress has a helpful feature that records video of test executions, helping you debug failures. However, this can quickly add up to excessive storage consumption, so Shubham Sharma advises on how to optimise it.

Google's Lighthouse is a helpful and easy-to-use tool for assessing web app performance. Pradap Pandiyan demonstrates how to set regular runs in CI.

You may have already heard of prompt engineering, but what about context engineering? In a 16-minute recording, Daniel Knott explains what it is and how it relates to Context-Driven Testing.

Speaking of the importance of context, Gil Zilberfeld points out why Your AI's Answers Are Subjective. Your Tests Don't Have to Be.

Create a problem, fix the problem, win... 😂

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