Welcome to the 76th issue!

This week, I stumbled something both entertaining and terrifying at the same time.

A story of a certain bug by Patrick McKenzie.

This is a reminder of how nasty some bugs can get.

I surely wouldn't like to be in Patrick's shoes. 😬

Happy testing!

Dawid Dylowicz

Kim Engel shares some interesting insights on the differences in coaching testers and developers. This is especially useful if you're currently trying to encourage developers to pay more attention to testing.

And if you want to learn more, Liz Keogh listed out 5 Rules of Coaching.

I'm always curious to read through deep reflections like this one shared by Lisi Hocke because there's a ton of lessons to learn from.

This is an important question. Although it's not so easy to answer, George Pirocanac provided several tips that can help you assess and make the best decision.

Someone on Reddit is looking for advice on what to pursue next after getting frustrated with testing. I liked the discussion there because it shows that there are plenty of opportunities for career development.

In this thorough article, Antoine Craske makes a fine point that quality is about culture and process, not testing.

And if that's not clear enough, take a look at the self-explaining title of Alan Richardson's write-up: (QA == Process) && (QA != Testing && QA != Tester && QA != Role).

Test retries are often a double-edged sword. They can help your tests look more stable but they may also cover real bugs. Andy Knight brought up a few great points on this matter.

If you want to learn more about analytics in web and mobile apps, this is the guide to follow. Anand Bagmar explained everything — from the basics to automation.

Speaking of measuring data for quality, Shivam Gohel shared a decent piece about Five Key Reasons Why Software Quality Metrics Matter.

Curious about using Appium with Cucumber in Java? Ekrem Kurt shared a detailed article describing how to set it up.

Additionally, André Ramos wrote a nice guide on getting started with mobile UI tests in minutes.

"You can't improve what you don't measure", goes the saying. And this is true in the context of testing, too. Svetlana Tkachenko shows a few examples of tracking test coverage statistics.

Testing a React Native project? Or maybe just curious about how it can be done? Gleb Bahmutov shows some code examples of tests written in Cypress.

Additionally, Stanislav Sopov wrote a Quick Guide to React Native Testing explaining various levels of tests that can be implemented.

This is yet another great article that Antoine Craske published recently. This one discusses the pros and cons of keeping tests in one or multiple repositories.

Looking for some handy Chrome extensions that can accelerate your testing? Gandharv Madan has put together this list of tools.

If that's not enough, here are another 10 Useful Chrome Plugins for Software Testers by Karolina Kożuchowska.

Testing in multiple environments is a common practice across engineering teams. Here's a guide by Ganesh Hegde on how to configure Cypress to easily run in each of them.

And if you want to speed the tests up, Gleb Bahmutov explains how you can Run Two Cypress Test Runners At The Same Time.

Performance testing as part of your CI pipeline is becoming more and more important. And thanks to Juan Pablo Sobral, now you can learn how to use the open-source k6 load testing tool for that.

There've been many articles about the upcoming Selenium 4 release but the truth is every article points out different things. Here, Arun Motoori explains the change in communication protocol with the browser and shares a couple of recordings describing some other changes.

The most important part of the CI/CD pipeline? Frequent delivery of stable software. Thomas Haver shared a detailed summary Automate and Enable Low-Risk Releases chapter from The DevOps Handbook.

"Hotfix"... 😂

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