Welcome to the 326th issue!

What's the impact of AI-generated code on testing?

We can learn more about it from the State of AI-Generated Code 2026: The QA and Testing Gap report by DeviQA.

It's the result of a survey of over 300 testers and brings an interesting point of view regarding the real productivity improvements with AI.

And if you're looking for further interpretation, Myke Ralduxin shares the Software Testing Trends in 2026.

Happy testing! 🙂

Dawid Dylowicz

I was in that position and I can relate to Callum Akehurst-Ryan's points on building a quality culture. Good read and good advice.

Kevin Bronsdijk explains why he stopped looking at long CVs full of tools and instead asks what someone has built, fixed or challenged in their last job to find the right candidates.

In relation to that, Jaclyn Leigh shares good insights into What I'm Learning From Sitting in Engineering Leadership Conversations.

If you think testing with AI stops at test generation, you're wasting its potential. Adrian How Zhiteng outlines the full workflow that runs from requirement checks to test automation with context.

A good read from Jitesh Gosai describing the problems with quality among different teams and explaining how to reach four levels of confidence.

Also, Ravi Rawal explains why Quality Is Not a QA Responsibility.

Marina Jordão has a good point on why we should be asking "what happens when this goes wrong" in refinement instead of jumping straight to acceptance criteria. At that stage, it's a cheap way to catch risks.

I believe we all feel the increased number of pull requests to review. Milan Bomjan Tamang shares a checklist for reviewing AI-generated code, covering assumptions and running automated tests before approval.

Milan also shares the outcome of an experiment: Can AI Write Better Test Cases Than a QA Engineer? I Tested It for 30 Days.

We all fight flaky tests, but do we do it right? Julia Pottinger walks through how to confirm genuine flakiness, read the trace for the cause and choose to fix, quarantine or delete the test.

On top of that, Bianca Ionescu advises to Stop Writing Unit Tests for Coverage. Instead, Ask What Bug the Test Would Catch.

Writing visual tests for an Android app? Alex Zhukovich gives two ways to stop async images from making your runs look different every time.

Additionally, Mayvin Ramasawmy explains how to achieve Parallel Mobile Testing, Part 2: Scale Across Devices and Turn It On.

Ujjwal Kumar Singh guides us through the setup of the first CI pipeline from scratch and shares lessons learned from that process.

Have you heard of the Screenplay pattern in test automation? Pudur Ramaswamy shares how implementing it helped fix a login bug that took three weeks to track down across a shared test suite.

On that note, Irfan Mujagić shares another take on test debugging: Give Your AI Agent Eyes: Capturing DOM Snapshots for LLM-Assisted Test Debugging.

If you're building multi-agent test workflows, Kostiantyn Teltov shows why agents should split by risk instead of by topic and why some steps are better handled by code than by AI.

Moreover, Julia Pottinger gives a good overview of Using AI to Generate Tests and Test Data.

Emna Ayadi shares results from a poll showing that most people now build their own test tools or use AI, rather than pay for enterprise platforms. I was genuinely surprised to see the results.

What's new in Cypress 16? Removes Cypress.env() to keep secrets out of the browser, reduces flaky tests and brings HTTP/2 for faster page loads in your tests.

Furthermore, David Ingraham wrote about another recent feature: cypress tap: Closing the Loop Between Your Agent and Your Suite.

If you want your Playwright suite to run faster (I mean, who wouldn't?), Mohammad Faisal Khatri describes how to use workers, sharding as well as how to avoid flaky tests and race conditions.

Also, if you work with Selenium, Roger Richards explains Understanding Smoke Tests in Selenium: The SimpleSmokeTest Approach.

Well, yes, you can use your Playwright tests for load testing, but should you? David Mello shares the wins, the two bugs it caught and where it stops scaling. This is followed by a good guide on AI Performance Testing Guardrails Every Tester Needs.

You may know Swati Seela from the articles I've already featured over the last few months, and now you have a chance to see and listen to her thoughts on AI testing. An interesting 40-minute recording hosted by Joe Colantonio.

Swati also asks: Should a QA/Tester With 10 Years of Experience Be Worried About the Current Job Market?

Good timing for those of you looking to take your Playwright tests to the next level with AI. Rex Jones II has just published a free video course. Enjoy!

Jira-driven development... 😂

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