Welcome to the 194th issue!

Good news, the 2023 State of DevOps Report is here!

It was created by Google and DORA, and while it's a huge 95-page document, it's full of great insights for enabling faster delivery of quality software at scale.

But if you're looking for a summarised interpretation of the results, Tomas Fernandez wrote a helpful overview.

Happy testing! 🙂

Dawid Dylowicz

This is a wonderful deep dive into bug triaging by Gleb Sarkisov, including a handy formula for calculating the bug priority.

There are a lot of great insights in this example of building a quality assurance process, based on Oleksandr Strukov's experience.

Moreover, Abiola Rasaq shares with us 5 Pillars of Software Testing Mastery.

Jason Arbon did a great job capturing tens of testing principles in concise one-liners. I found them surprisingly accurate.

Testing is a heavy mental activity. So it's important to know the psychological tricks we're prone to, as Kristin Jackvony greatly explains.

Furthermore, Michael Bolton advises testers to do things Out of Order.

Arkadius Wellyam correctly points out the potential problems with chasing 100% test coverage.

While we can't completely avoid flaky tests, we can control how we respond to them. Here's some good advice from Leonardo Booth on what to do.

In that context, Manish Saini reminds us about the Essential CI Triggers for Your Test Automation Pipeline.

João Coelho explains how fuzz testing can help you find hidden issues and vulnerabilities with some of the open-source tools.

It may also help reduce the Cyclomatic complexity: Why QAs (and Devs) should worry about it, as Rodrigo Matola explains.

Sam Gladstone wrote a thorough overview of effective testing from a user perspective, supported by the Testing Library and the principles behind it.

Max Perepelov reminds us to focus on smarter test automation by investing in shifting left and ensuring that tests have the right purpose.

A good complimentary read to that is Paul Grandjean's take on When to Write Automated Tests vs When to Rely on Manual Testing.

In this comprehensive overview, Rafael Miguel explains why and how tests can become a safety net during code refactoring.

Speaking of which, you may want to see Gleb Bahmutov's detailed Test Refactoring Example.

k6 has created an amazing guide to automating performance testing, including an example test plan. It's applicable even if you're using other tools.

On that note, you might also be interested in NaveenKumar Namachivayam's recent helpful solution — Introducing the Apache JMeter Docker Extension.

The new JavaScript test runner in the town — bun test — promises lightning-fast test execution. Here's a good comparison to other popular test runners by Irfan Mujagić.

Furthermore, you may want to learn How to master Jest Config for your JavaScript projects from Phillippe Santana.

Playwright is a versatile tool that comes with API testing capabilities, which Numanhan Duran explores in this article.

And this comes in contrast to what the community thinks about Automating API Tests with Cucumber, the worst choice?.

Andrey Enin did an interesting analysis on one of his projects to determine what type of Playwright assertions are the most common.

Moreover, Beth Clarke explores E2E Testing with Playwright for Python: Pros and Cons.

Fixing a bug in production... 😂

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