Welcome to the 294th issue!

Now, that's impressive.

Spotify has built a solution based on AI agents to automatically create, test and merge code changes for migrations and dependency updates:

• 1,500+ PRs Later: Spotify's Journey with Background Coding Agent (Part 1),
• Background Coding Agents: Context Engineering (Part 2).

I must say, this level of confidence requires some solid quality gates.

Kudos to Max Charas and Marc Bruggmann for sharing the details.

Happy testing! 🙂

Dawid Dylowicz

We know that AI is here to help us, but we also need to use it wisely. Joel Wilson gives some advice on where to leverage and where to be careful with AI in testing.

Similarly, Maaret Pyhäjärvi shares a process of developing a Habit of AI in Quality Engineering, while Ioannis Psaronikolakis wonders — Does AI Mitigate QA Curiosity?.

Agile Testing is all about a whole-team approach to quality and testing. Nicola Lindgren explains how to get others involved.

Moreover, Keith Klain shares some thoughts on the (Testing) Mind over (Developer) Matter(s).

This is a wonderful series of articles by Huib Schoots explaining the foundational concepts of how we could approach testing. You can already read the following parts: 2, 3, 4, 5.

Also, Callum Akehurst-Ryan advises that if you Want to be a better Quality Engineer: Lose the Ego.

What is quality? It's a tricky question, and rather than seeking the ultimate answer, it should make us reflect. Just as Maaike Brinkhof did here.

Furthermore, Janine Nguyen issues A Public Apology To Engineers From Someone Who Has Watched Quality Fail.

This post drew some attention from software testers on Reddit, and rightly so. I mean, who hasn't faced such a problem at least once?

In a related thread, someone asked: How do you handle "won't fix" / known issues in your team?, while others are discussing Building a QA Dashboard in Jira to show the metrics.

Yusuf Özgül shares an insightful overview of how they approached an iOS testing pipeline at scale and the challenges associated with it.

Similarly, Osama Sayed proposes a CI/CD Pipeline For Android.

Interested in trying something other than the Page Object Model? Nai-Yuan Chang describes an intriguing approach using a layered architecture.

Moreover, Mohammad Faisal Khatri shares an in-depth overview — What Is Page Object Model (POM) Design Pattern?

Testing LLM models? While setting up the evaluation framework, you can start with a mocked solution first to avoid unnecessary costs, as Irfan Mujagić demonstrates.

Looking to shift testing left? Ned J. advises creating several layers of checks before pushing to the repository, such as automated tests, commit hooks and isolated environments.

In relation to that, Okan Yenigün describes using Contract Testing as a Formal Agreement Mechanism for Reliable API Interaction.

Wondering how to structure your test framework? Aykut Denizci and his colleagues share insights into the approach they implemented for one of the projects.

What's more, Albert Ścibor tells us about the Layers of Verification: Why Full E2E Coverage Is the Wrong Dream.

Appium is commonly used for mobile test automation, but did you know it can also test desktop apps? Rohan Dudam demonstrates it, followed by a helpful article on How to use Appium Inspector along with Windows Inspector.

Liudas Jankauskas created Rentgen — an open-source tool for robust testing of APIs. If you're curious to learn about the outcomes, he also shared a follow-up.

In this detailed article, Nigel Mulholland shares his impressions from trying out CodeceptJS to write clear-to-understand automated tests in JavaScript.

Wondering what API calls your UI tests do? Thananjayan Rajasekaran shares a custom solution for enhancing Playwright test reports.

Also, Ganeshan Manickam provides a high-level overview of Building Your Own Playwright Test Healer with AI Agents.

If you automate testing Spring Boot applications, you may want to learn from Philip Riecks about the new features brought by a recent major release.

Want to learn more about contract testing? Nicola Lindgren gives an overview of a fairly recent Contract Testing in Action book by Marie Cruz and Lewis Prescott.

In this 14-minute recording, Alan Richardson demonstrates how to use OpenCode and your browser to automate Selenium tests. And if you prefer reading, check out this article.

Last week, Karthik K.K. showed us how to migrate from Selenium to Playwright using AI. This time, it's Cypress' turn.

Cooking vs coding... 😂

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