Welcome to the 296th issue!

This time, I'm sharing with you a Reddit thread that I particularly enjoyed:

New CTO pushes feature testing to Dev while QA owns quality outcomes.

It sparked an intriguing discussion on shift-left testing, potential quality risks, and lessons learned from this approach taken in other companies.

I believe this is generally the right direction, but it requires careful implementation and support on both the development and testing sides to make it work.

So that's why I also recommend reading A developer's guide to caring for software testers by Olly Fairhall.

Happy testing! 🙂

Dawid Dylowicz

David Ingraham shares great advice on building the right culture within a QA team that can effectively support the organisation.

Furthermore, Alan Page correctly outlines why Leadership is a Constant Experiment.

What workflow pipeline do you use in your team? Anton Faibyshev describes in detail the approach they took to improve collaboration and quality delivery.

At the same time, Higor Mesquita advises on How to Deal with Stressful Deadlines as a QA.

Getting the naming and definitions in testing right is as important as it is hard to achieve. Joep Schuurkes outlines a few reasons why.

Similarly, Gary Hawkes reminds us that We Shouldn't Be So Obsessed With Our Industry Terminology.

The evolution of AI and the changing market forces have led some companies to believe that cutting testing teams is the way to go. But it isn't without the risks, as Ryan Craven points out.

Perhaps they should listen more to Hannah G. Anulur's thoughts on Redefining QA in the Age of AI and Robert Meaney's reasons leading to The Quality Death Spiral.

Callum Akehurst-Ryan raises some good points about the importance of shift-right testing practices that may not be as popular among the testing community as shift-left ones.

Two weeks ago, I highlighted Spotify's story of creating AI coding agents that autonomously support their development. This is the third (and the most interesting to me) part outlining the challenges in testing that solution by Max Charas and Marc Bruggmann.

Furthermore, Irfan Mujagić shares The Complete Guide to RAG Quality Assurance: Metrics, Testing, and Automation.

Jatinderpal Singh Toor describes how they built an agentic AI solution that generates test documentation in Jira tickets with a single Slack command. Another clever example of leveraging AI to support testing processes.

Struggling with slow Pytest tests? Anatoly Bobunov explains how parallel runs, better waits, and cleaner data drastically reduced their test execution time.

What's more, Ian Göbl shares great insights into Kota's Method for Reliable Integration Tests.

Asserting is generally easy — it's either a pass or a fail. However, testing the AI's output is not that straightforward. That's why Gil Zilberfeld developed a scorecard to help determine test outcomes.

Moreover, Oliver Martin-Hirsch shares several high-level Practical Ways to Test AI Across the SDLC.

How do you track the test distribution of the test pyramid? Taras Mankovski points out why it's important to understand which tests are implemented at each layer.

Also, Senura Fernando points out why Architecture Tests Are the Missing Layer in Automation.

If you need to test Android app flows that use the camera, Khaled Sayed Ramadan demonstrates a simple script that places a custom image in the preview during automation.

What's more, Josphine Job demonstrates How I Fixed Slow Appium Tests with Single-Session Management.

Facing flaky web UI tests because of the bot detection? Sit comfortably and enjoy this long but insightful guide on how Toni Maxx built an automated solution to address this problem.

Guna Shekar R gives some great, practical tips for building a Playwright-based API test framework that's well-designed, stable and effective at once.

Gleb Bahmutov demonstrates how a TypeScript feature can help you write more resilient tests. The example is in Cypress, but it applies to other frameworks, too.

Moreover, Anuradha Liyanage wrote a handy guide to Mastering Cypress Network Requests & API Testing.

XCUITest is the native test framework for iOS mobile test automation. Josphine Job tells us about the benefits of using it and what lessons they learned along the way, followed by 7 Proven Patterns for Maintainable XCUITest Suites.

In this 10-minute video, Karthik K.K. comes to a conclusion on the popularity of test automation tools based on various data points. Are you surprised by the results?

Automatic bug fixing... 😂

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