Welcome to the 299th issue!

Today, I have a great resource to share with you — 100 Insights into Quality Engineering.

It's a series of short notes compiled by Jitesh Gosai from various sources in 2025.

And based on that, Jitesh described the Three Quality Engineering challenges of 2025, and what to do about them in 2026.

Enjoy and happy testing! 🙂

Dawid Dylowicz

Whether you're already using or planning to use AI, Marina Jordão gives some great advice for test teams on how to do it right.

On top of that, Yogesh Deshmukh brings up a few interesting points on Why You Can't Use AI for Testing Until You Know How to Test AI.

It's tempting to use AI for testing, but Konstantinos Konstantakopoulos points out that we shouldn't forget to value human judgment and analysis.

Similarly, Nicholas Ofonagoro shares his thoughts about working with AI — Test Automation & AI: ChatGPT… Please Take My Job!.

Fred Hebert shares a wonderful, thought-provoking article about the constant battle to find the right balance between speed and quality in software.

Also, George Ukkuru notices that sometimes QA Keeps Testing Rules Nobody Can Explain.

I like Jeff Nyman's take on risk described in this article.

Moreover, Keith Klain explains why Testing Shapes Reality, especially in the age of AI.

A sobering reminder from Abiola Rasaq that you should constantly try to evolve your testing skills and approaches in order to keep growing in your role.

Also, Stuart Thomas describes how we should perceive our role: Quality Engineers — Who Are Your Customers?.

Do green pipelines really mean you're safe? Mona M. Abd El-Rahman explains why focusing too much on automation can hide some risks that can be exposed by other ways of testing.

Mona also advises on Designing API Test Coverage for Microservices that focuses on testing the right things.

Wondering how you can bring more shift-right testing practices to your company? Artur Burov gives examples of chaos engineering, synthetic monitoring, contract testing, and more.

Speaking of DevOps, you may want to learn about The Real Cost of a Slow CI Build from Dennis Martinez's observations.

While not common, mutation testing can be a powerful way to verify your tests' resilience and challenge assumptions about your system behaviour. Bas Dijkstra wrote a good high-level overview of that.

Alper Önal demonstrates how they automated AI-powered test generation using proper practices such as POM, MDC, and DSL.

Furthermore, Beth Marshall describes How I Built an Agentic SDLC Demo with Cursor, MCP Servers, Playwright, GitHub, and Vercel in Under an Hour.

Struggling with failing locators? Akın Sancar and Cansu Gökay share a detailed, example-based story on how they implemented a solution to auto-heal XPath-based locators with AI.

Wondering how to speed up your pipeline? Gleb Bahmutov shows a detailed guide on how to cache dependencies within a Docker image and implement this solution in CI for Cypress.

Using Playwright for API testing? Then you might be interested in different ways of checking responses, as advised by Mohammad Faisal Khatri.

If you're working with APIs, you may like it. Liudas Jankauskas created Rentgen — an open-source test generation and validation tool. You can find out how it works directly in the repository.

If you haven't heard of the popular BugMagnet browser extension yet, in this 8-minute recording, Daniel Knott explains how it can help you test websites.

David Burns invited Keith Klain for an intriguing, 40-minute discussion about the future of testing in the age of AI.

Smoke testing... 😂

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