The Quality Trail: May 2026 QA News
From the Desk of the Editor
If you have been reading this newsletter for the past few months, you have probably noticed a recurring theme: AI. At the risk of sounding like a broken record, it’s everywhere right now.
No one will dispute that we are in the middle of a massive industry shift. Whereas 6 months ago the question was “should we use AI?” or “how do we get people to use AI?” We’ve moved on from the era of AI co-pilots to the dawn of autonomous and agentic testing.
As we settle into Q2, a clear divide is emerging in the QA testing market. On one side, we have AI-native startups building platforms from the ground up around agents. On the other, we have every other platform (many of them legacy test management platforms) bolting AI onto decades-old UIs.
As leaders, engineers, and service providers, it is our job to cut through the noise. “AI slop” is everywhere we look, and code is cheaper to generate than ever, though it’s often buggy and difficult to maintain. The bottleneck is no longer creation but validation, which makes the role of the QA professional more important than ever before.
So, in this edition, we take a brief step back from AI to look at fundamental engineering resilience. We dive into chaos engineering for microservices and provide resources on how to navigate this latest transformation with confidence.
As always, let us know if you think we missed something, or drop us a line any time with your thoughts. You can also sign up to receive these testing updates via email.
– The QualityLogic Editorial Team
What’s Inside
- Testing Resilience with Chaos Engineering
- Upcoming Conferences and Events
- What We Are Reading
- Learn More
Testing Resilience with Chaos Engineering
While the industry debates the future of autonomous AI agents in software QA, the reality of testing distributed microservices remains one of our most complex daily challenges. Keeping up was typically possible in the past, but with the rapid pace that AI enables software engineers to take, verification debt becomes a compounding issue, especially in a client that employs the distributed microservices architecture.
In a recent deep dive, Tito Irfan talks about how Software QA Engineers Test Resilience in Distributed Microservices. The term, distributed microservices, was coined by the team at Netflix, who built a tool called Chaos Monkey (now available open source) which randomly terminates their production instances. Yes, you read that right.
The idea is for Chaos Monkey (and other forms of chaos engineering) to ensure that engineers build fault-tolerant systems. Rather than relying solely on traditional functional testing, chaos engineering forces teams to intentionally plan for failures since they know they are going to happen anyway. If you treat network latency, dropped packets, and server crashes as standard practice, you never have to worry about the implications in production, because you already know how the system will degrade and recover.
To be clear, we’re not recommending everyone adopt this approach. It would only work in a distributed microservices environment and may not be what you want. However, for QA teams transitioning from monolithic architectures to microservices, the testing paradigm has to shift: just testing the happy path or even the known edge cases is not a good QA practice. You have to test the unknown edge cases by actively breaking things in controlled environments.
If your testing strategy assumes the network is reliable and servers do not crash, your microservices are not actually ready for production.
Upcoming Conferences and Events
- Live2Test: June 2 – 3 (online): A premier annual online conference dedicated to Software Testing and Quality Assurance (QA) designed for testers to communicate, learn, and share insights.
- Innovate QA: June 4 – 5 (Bellevue, WA): Join industry leaders, pioneers, and visionaries sharing insights, best practices, and cutting-edge tools to build high-quality, safe, accessible, and reliable systems. This year, they have leadership, practitioner, and demo tracks.
- QA or the Highway: June 12 (Columbus, OH): One-day event designed for QA specialists, test automation engineers, and development leaders to learn hands-on strategies, testing trends (such as AI-assisted testing), and software culture. It sets itself apart by being a smaller event (around 400 attendees) which provides an opportunity for more direct learning and conversation.
- EuroSTAR Software Testing & QA Conference: June 15 – 18 (Oslo, Norway): One of the premier software testing conferences in Europe. If you are looking to connect with the broader QA community and dive deep into both agile testing and DevOps practices, this is the place to be next month.
- PNSQC 2026: October 12 – 14 (Portland, OR): The Pacific Northwest Software Quality Conference is the only peer-reviewed QA conference in the U.S. While the call for papers has closed, they are still looking for poster paper proposals.
For the full year-round list, testingconferences.org remains the best single resource.
What We Are Reading
We keep tabs on the news in the industry, so you don’t have to.
- Playwright vs Cypress vs Selenium: 2026 Comparison Guide – Testomat: A fresh, detailed breakdown of the big three automation frameworks, covering test stability, auto-wait mechanics, and architectural differences affecting modern test suites.
- Selenium Alternatives in 2026: Playwright, Cypress & More – Quash: Explores why teams are moving away from Selenium, the factors that make people lean toward Playwright, and where Cypress fits in.
- Anyone Can Build, Almost No One Can Maintain: The Real Cost of AI Coding – Hany: A sobering look at the long-term QA and maintenance burden of AI-generated codebases.
- How to Triage Bugs Without Losing Your Mind (Or Your Team’s Trust) – Terrible Freedom: A framework to help manage the organizational and emotional friction of bug triage including severity vs impact, criticality, score calculation, and prioritization.
- Claude Code for QA: The Agentic Workflow That Will Save You 100 Hours – Anton Krylov: A practical guide to leveraging Claude Code’s agentic capabilities specifically for testing and QA workflows.
- Claude Code Hooks as a Test Quality Gate – The Green Report: Explores how to use automated quality gates with AI coding assistants to cut down on issues before the code is written.
- Test Smart: How to Approach AI and Stay Sane – UX Design: Strategies for approaching the testing of AI applications without getting overwhelmed by their non-deterministic nature.
- Vernon Version 3 – Now With Added AI – Yeah But Does It Work: A practical look at the realities of AI and the identity shift the author is adopting to fit in this new world.
- Modern Test Management: 7 Features Executives Must Demand in 2026 – Rahul’s Testing Titbits: In an AI-accelerated world where code is cheap, but validation is costly, traditional test management tools (focused on test case execution and narrow reporting) no longer give leaders the insight they need to make safe release decisions. This post lays out potential solutions to that problem.
That’s All for Now!
That’s a wrap for this month. Until next time, keep testing, keep learning, and keep pushing for quality!
Interested in More Information About QualityLogic?
Let us know how we can help out – we love to share ideas! (Or click here to subscribe to our monthly newsletter email, free from spam.)