Welcome to the 119th issue!

Hope you had a good week and you're off to a well-deserved break.

But before you go, I want to share with you three sets of short tips for software testers that I found valuable this week:

1. 24 Lessons from Working in Software by Andrew Knight
2. 21 Tips for QA Professionals by Manish Saini
3. #21Days21Tips by Matthew Middleton

Happy testing!

Dawid Dylowicz

How should you test a monolith? Kevin Coulombe suggests checking the test coverage and using The Testing Trophy strategy.

Taking notes while you test is a powerful practice. James Thomas shares a few tips from his experience on how to do it well.

In relation to that, Bob Salmon brought up some interesting Analogies and objectives for testing, explaining why testing is about information hunting and more.

Vishal Lad shows an example of calculating a quality score for services and applications using various signals: from test coverage to bug counts.

Bob Salmon shares with us three handy techniques to test an ETL data pipeline that focus on the content, the consistency and the output.

While there might not be one that works in every case, Kristin Jackvony describes the pros and cons of various possible ratios. Personally, I also consider the 1:1 tester per product manager ratio as an option.

Similarly, someone asked on Reddit: How to divide work between 2 testers in the same team?.

Antoine Craske shares a few helpful practices that can help you build quality in your software development life cycle.

Moreover, Antoine also wrote about Setting Goals with OKRs In Quality Engineering.

If you're planning to move to test automation, Olesia Martushkanova has some tips and lessons learned on how to successfully go through that journey.

Good advice for testing apps in the serverless architecture.

Vaibhav Saraswat faced the interesting challenge of making his tests run offline and sharing what they learned from that.

Michael Küsters uses insightful examples to show why relying solely on test coverage metrics might not tell us the full story about the quality of our product.

Ever run into problems using WebDriver? Cagri Ataseven has some good advice on how to solve the common ones.

If you want to get more visibility of what's going on in your Cypress tests, here's a simple tip from Boris Arapovic on using the decorator pattern to improve your logs.

In addition to that, Ginta Purina wrote about Useful Information QA Engineers Can Find in Application Logs.

In this cheat sheet, Alexey Anisimov shares a few clever tips that can make your testing with Docker easier.

While this handy list of books by Tomas Fernandez is generally targeting software engineers rather than testers, you may still find some relevant reads to your role.

Every night... 😂

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.

PS. I'll be transferring every donation to Nasz Wybór Foundation which supports Ukrainian refugees in Poland. 🇺🇦 🙏

Dawid Dylowicz