Welcome to the 203rd issue!

This time, I have something very insightful to share with you:

20 Lessons Learned From 20 Years in Tech: Part 1 and Part 2.

Written by Dennis Martinez who worked on a lot of projects as a consulting software engineer, including test automation.

Having experienced so much, I truly find his insights valuable.

Thanks for sharing, Dennis.

Happy testing! 🙂

Dawid Dylowicz

In a three-part article, Bharat Varshney shares a lot of practical pieces of advice on how to become a better tester. Here you can read the second and the third parts.

Also, Filip Hric shares an interesting point of view on Testing as an entry gate to IT.

Ivy Murphy explains how Developer Experience and Quality Assurance functions can support developers and contribute to overall team success.

However, as Karla Mieses points out: Let’s be honest, in some places, QAs are not respected by other team members.

If you want to set objectives for your QA team, Putra Agung Pratama advises how to do that, using metrics and examples.

Speaking of metrics, Melissa Fisher came up with an interesting one: Test coverage — how about quality coverage?.

Michael Bolton explains the common confusion in understanding the difference between quality assurance and testing

Similarly, James Thomas describes what it means (and doesn't mean) to Build Quality.

How often do you find yourself running out of time to finish testing? Wayne Roseberry has some good advice on what to do in such a situation.

Facing challenges in test automation? Bharat Varshney points out what you might be doing wrong in terms of practices and testing patterns.

Bharat also shares valuable Advice for Clean, Modular, and Maintainable Test Code.

If you want to learn how a big bank approaches the test automation strategy, check out Ashish Ghosh's detailed overview.

Furthermore, Paul Grizzaffi uses a cooking metaphor to explain the potential problems with Multiple Automation Tools, Effort, and Messes.

Have you heard of the concept of "sociable" tests? Rafael Miguel explains with examples what it means and when such practice might be useful.

Similarly, Gil Zilberfeld continues the series about Abstraction and Testing — The Other Side.

Peter Flook describes in detail how to effectively use an integration testing strategy, especially around the data flows.

On that note, Roy Straub reminds us to Stop Testing Implementations.

Looking for a free test reporting solution? Denis Peganov wrote a helpful overview of five selected tools for different scenarios.

Sometimes you may take test tools for granted, but it's important to know how they really work. Here, Millan Kaul describes Appium in a simple way.

Someone on Reddit listened to the community's feedback and created Automize — a free, versatile Chrome extension for easy test implementation in many common test frameworks.

Following the first part, Adrian Maciuc shares several more handy tips for writing tests with Playwright.

Also, in this handy guide, Jan Molak explains how to Extend Playwright Test with Serenity/JS and leverage the Screenplay Pattern.

There've been many articles comparing Selenium to other tools. So many, that David Burns — one of the key Selenium contributors — decided to officially address these claims.

If you're curious about the potential trends in testing in 2024, Daniel Knott shares his predictions in this 17-minute recording.

In this 51-minute overview, Kacper Ciepielewski explains what types of tests should and shouldn't be automated.

Some bugs are features... 😂

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