Welcome to the 108th issue!

Do you know How They Test?

It's an amazing collection of the best resources about how various companies approach quality and testing.

And it's massive!

Some of the early subscribers of this newsletter may remember me sharing it already back in 2020.

But it's one of these dynamically growing projects that are worth highlighting once in a while.

And since the last mention, it's grown a lot.

Kudos to Abhijeet Vaikar for curating it.

Have a great weekend everyone.

Happy testing! 👋

Dawid Dylowicz

What's the difference between a good, great and word-class test team? Simon Prior explains that and gives five pieces of advice on how to build one.

In response to that article, Amit Wertheimer asks: A world class test team?. It's interesting to see both perspectives!

Engineering metrics are great but only if done right. Here are the common pitfalls that Mojtaba Hosseini has seen in his career.

A good follow-up read to that is A View of Metrics and Measurement by Jay Trommer.

What does agile testing really mean and how should you do it right? Here's a good reminder from Marcin Ludzia.

Similarly, Kinga Witko wrote about Agile testing — organized chaos or a planned way of improving your software?.

Here's a great food for thought shared by Jason Arbon who points out why testing is such hard work.

Antoine Craske highlights the key areas to focus your development on in order to become a skilled and valuable test engineer.

How do you achieve good test coverage in a service-oriented architecture without the maintenance hell? Christian Nissen has a few great ideas.

In relation to that, Dan Edwards wrote a decent piece about Testability Is An Architectural Choice.

Eldad Uzman demonstrates in a very clear way how mutation tests work using Cosmic Ray — a Python library — as an example.

In the last article of a great series of building a test automation framework in Java from scratch, Tomasz Buga shows how you can improve the framework with a builder pattern, libraries and tools such as Rest Assured for testing APIs.

On top of that, Matt Bailey explains why it's beneficial to do Preemptive Parallelism early in your test automation.

Bruno Lombardi gives a great lesson on the rules of unit testing and backs it up with solid examples in JavaScript.

On top of that, Vaibhav Chanana shows why Your test cases should fail and why it's crucial to add verbose assertions.

What if you could specify what tests you want to run by checking boxes in your pull request description? Well, Gleb Bahmutov did just that. Incredible!

Charles Chen gives a great high-level overview of Playwright — an open-source tool for end-to-end testing — and compares it to the other popular tools.

If you want to learn how to run performance tests in Java, Philip Riecks put together a full-of-examples guide to Gatling.

Looking for a read that can help you in testing? Mike Vaida shared a huge collection of testing-related books. There are some great suggestions in the comments, too.

"Buglog"... 😂

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