Welcome to the 160th issue!

This week, I found an uplifting discussion on Reddit:

What's your coolest achievement as a tester?

It's really interesting to see all the different things people are proud of.

It's also great to see all the hard work that goes into testing and the amazing things that come out of it.

Happy testing! 🙂

PS. The discussion also continues in this thread.

Dawid Dylowicz

Gleb Sarkisov came up with a modified formula for calculating the Defect Density metric and described this process in detail.

Furthermore, Dmytro Stekanov wrote a great article on Ensuring Quality in the Product Backlog: The Role of QA in Refinement.

Bruna Chagas advises on how to change the team's mindset and empower everyone to participate in testing activities.

Similarly, Liis Pass describes the process of Moving towards Modern Testing Practices: Easy Steps for Improving Your QA Processes.

Someone asked this question on Reddit and testers responded with several interesting scenarios.

In relation to that, Vincent Ferreira shared his journey From Developer to QA: Benefits of a Career Shift.

In this honest article, Michael Bolton shares his thoughts on why testing can put us in uncomfortable situations and provides guidance on how to navigate that.

Amit Wertheimer explains why quality is hard to define and why it should be broken down into specific qualities and properties instead.

Furthermore, Bart Vanherck reflects on the core principles of The Agile Manifesto.

Based on the experience of maintaining frequently-ran tests, Tom Perry shares what practices helped them improve pipeline stability.

Similarly, Christian Nissen gives a few tips on Effectively Reducing the Run Time of Automated UI Tests.

Continuing the series of articles on testing serverless apps, Ran Isenberg shows examples of different test levels. You can also read the first part about best practices.

Moreover, Zane Scheel wrote a good article about A Taste Test of AWS Services for the Software Quality Engineer.

If your team works in Scrum, you might be familiar with story estimation. But how do you apply it to test automation tasks? Mohamed Yaseen wrote a thorough guide.

Sometimes the proven solutions are best. Torsten J. Zelger shares the story of implementing a test automation framework several years ago that still works fine for them today.

Christian Findlay explains why implementing the right test type is more important than trying to meet a certain test coverage metric.

In relation to that, Rafael Miguel describes in detail the benefits of Using Branching Coverage to Improve Software Quality.

Here's an interesting overview of tools that testers use regularly. They vary from IDE, Chrome extensions and bug-tracking tools.

Speaking of which, Anshita Bhasin wrote a Detailed Guide to Chrome Dev Tools.

If you're interested in API testing, Mohammad Faisal Khatri shares a thorough guide to Playwright for Java and TestNG.

Similarly, Butch Mayhew describes the Basics of API Testing with Playwright.

In the second part of the series, Alex Sanzhanov describes how recursion can come in handy in Cypress tests. You can also read the first part about loops.

Testing iOS mobile apps? Alexey Alter-Pesotskiy explains how to use XCTContext for writing tests in the Given When Then style.

Max Stahlschmidt describes a brand new open-source tool — Balder — which allows you to reuse a once-written test code across different platforms, devices or applications.

Did you know that Playwright has a built-in solution for visual testing? Balaji Kumarasamy shows a few examples of using it.

Dev vs QA... 😂

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