Welcome to the 202nd issue!

Today, I want to share with you an intriguing research paper on the role of Software Quality in Developer Productivity.

It's been written by the Engineering Productivity Research team at Google and it's full of insights on the theory of quality and its potential impact.

You can also read this handy summary by Abi Noda.

Happy testing! 🙂

Dawid Dylowicz

Do you need QA in Agile? Bharat Varshney answers this question and explains the tester's role.

There are many testing practices and principles — but which ones are the most useful in practice? You can find several interesting examples in this thread.

Also, Mike Harris explains why Developing your listening skills is really useful.

Srinath Perera describes two main metrics that matter in performance testing and then gives a few examples of running such tests.

What does it take to be a QA Lead? Hardik Chotaliya shares some good pieces of advice based on his experience.

Kristin Jackvony explains what makes testing inefficient and advises what to do in each case.

Similarly, Jeff Nyman advises focusing on the three key pillars: testing, testability and automation, in his Scrutinize, Stabilize, Sustain article.

In this article, Burcu Akkaya shows how you can set up and use WireMock to improve API testing.

Also, Gil Zilberfeld wrote a concise article explaining Abstraction and Testing — Mocks.

Mahir Berk Canan and Esra Cebeci describe the strategy and implementation of tracking iOS UI test automation during development that they implemented.

Moreover, Bharat Varshney explains how we can benefit from Leveraging Test Automation for Seamless Iterations in Scrum.

If you want to learn about setting up robust CI for iOS development and testing, Alberto De Bortoli wrote a detailed guide.

It's especially important if you want to implement a Release Train in mobile development, as Maxim Kachinkin explains.

What does it take to set up a test framework? And how can you do it? Irfan Mujagić wrote a wonderful series of articles explaining it step by step. Here are the part 2, part 3, part 4 and part 5.

You may also want to create Testing API (TAPI), as suggested by Michael T. Andemeskel.

There are different ways of managing and structuring your tests. Andrey Enin gives a few tips depending on the setup.

And once you have the structure sorted out, you may want to look into creating Custom Assertions for Cleaner Code, as per Elias Nogueira's advice.

Continuing the great series of comprehensive articles on testing mobile apps with Appium, this time Lana Begunova shows how you can extend the tool's capabilities with some helpful features.

Want to get more clarity in your Playwright test reports? Butch Mayhew demonstrates the indent-test-reporter library built specifically for that.

Nicola Gallazzi shows how to leverage the new testing API for UI testing of Android apps, enabled thanks to the Jetpack Compose toolkit.

There are a lot of debates around the best test tools for web testing, and here's Zhimin Zhan's perspective on the current state.

If you want to learn about contract testing and how to implement it using Pact, here's a decent guide with an implementation example.

This is a great, 35-minute conversation on leveraging test automation design patterns between Anton Angelov and Nikolay Advolodkin.

In relation to that, Gil Zilberfeld recorded a 46-minute video about best practices for writing Clean Tests.

Want to learn Playwright in Java? Pramod Dutta recorded a two-and-a-half-hour tutorial that guides you through all of its aspects.

CTRL+CCCCCC... 🤣

Thanks for reading!

If you like this newsletter and it helps you become a better tester, you can say thanks and buy me a coffee.

Dawid Dylowicz