Welcome to the 89th issue!

This week, I found an interesting thread on Reddit asking software testers:

What's the worst bug you ever missed?

It's a great read for two reasons:

1. The advice on not taking the blame personally.
2. The actual bugs.

Happy testing!

PS. Due to an arm injury, I've hired a technical writer to help me polish the descriptions for this issue, most of which I had previously captured using the brilliant speech-to-text Drafts app.

Dawid Dylowicz

Have you ever been asked about what percentage of your test cases are automated? James Thomas raised a few good points on why this question isn't valid.

In a similar fashion, Vladimir Tiulenev shared his opinion about measuring Test Coverage.

Callum Akehurst-Ryan describes a very interesting concept of Charisma Testing — a technique where instead of looking for flaws, you focus on the good things.

What an important article! A lot has been said about how soft skills can help software testers but here Jess Ingrassellino focuses specifically on how to increase your influence within the team to become an informal leader.

Wondering how a typical day of a tester looks like? Although it may differ from role to role, Jolivé Hodehou captured the essence.

Also, Senuri Samindi elaborated a bit more about the differences between The role of Test Manager vs. the role of Tester.

Whether in life or in testing, it's always good to have a few plans. Maaret Pyhäjärvi shares 3 of them: a one-page test plan, a test strategy plan and a test environments plan.

What's wrong with the Page Object Model? Eldad Uzman once again brings up some valid ideas and examples proving his point. You can also read Part 1 that mentioned two weeks ago.

Additionally, Murat Ozcan gives an amazing explanation of why Page Object is not the ultimate solution, using multiple examples from Functional Test Patterns with Cypress.

Continuing the great series on API testing, Pricilla Bilavendran and Priyanka Brahmane show you how to use the data-driven test approach for one of its best use cases — APIs. They used popular tools, such as Postman and Karate, as an example.

In this concise article, Han Toan Lim shares an example of using the DRY principle for designing and refactoring automated tests.

Interested to learn how Vimeo tests their UI? Andrew Katsikas reveals some of the practices and tools they use.

Furthermore, you might be also interested in Cesar Lugo's story about the Adoption of engineering standards at Typeform.

How do you decide whether you should write unit, integration or end-to-end tests? Nicolas Carlo shares some great pieces of advice on how and when to implement each of them.

In a similar context, Jaswanth Manigundan wrote about his Recent Obsession with Hermetic Tests for mobile.

It's important to strike a balance between manual and automated tests. Simon Knight gives a few great tips on how to decide when to do which.

Similarly, Eduardo Fischer wrote about Test Automation: Always The Approach Of First Resort?.

Postman is a very versatile tool and Maciej Seleman shows how you can implement a custom script for running load tests and even export the results to create a graph.

Yusuf Tayman wrote a clear article demonstrating how to use k6 for performance testing of databases. Looks simple!

Looking for a UI testing tool for Android? Harish Rajora put together a list of six and listed out the pros and cons of each.

Additionally, Junaid Ahmad presents how to use the Kakao tool to Write First UI Test in Android.

If you use Java, you might be interested in Guilherme Rogatto's overview of TestContainers that can help you set up the whole testing environment on Docker.

The new version of WebDriverManager 5 — the open-source library for managing Selenium in Java — has been recently released and Boni García describes the key changes in this major release. You can also have a look at the changelog.

NaveenKumar Namachivayam gives an excellent overview of The Hitchhiking Guide To Load Testing Projects book about load testing by Leandro Melendez.

When life gives you bugs... 🤣

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