Welcome to the 209th issue!

Big news from Netflix! They released a new test library:

Introducing SafeTest: A Novel Approach to Front End Testing.

You can find the GitHub repository here — kudos to Moshe Kolodny.

And if you're curious about the first-hand experience, Nikolay Advolodkin recorded a Live Coding Session with SafeTest.

Happy testing! 🙂

Dawid Dylowicz

Wondering what bug advocacy is about? Here's a great explanation by Maaret Pyhäjärvi, including a list of tactics to make the most out of it.

In relation to that, Mohit Verma uses visual metaphors to warn us about Recipe for Disaster: The "Don'ts" of Bug Reporting with a Dash of Humor.

Janet Gregory shares a helpful, concise definition of the role of a Quality Coach while recommending some follow-up reads.

Furthermore, James Thomas gives some valuable advice on The Best Laid Test Plans.

Here's an interesting summary of James Bach's take on the current challenges in testing suggesting a shift in our approach to testing education. You can also listen to the full episode there, hosted by Darko Fabijan.

Joep Schuurkes describes what it takes to be a tester nowadays and gives some practical advice for newcomers.

Similarly, Dennis Martinez shares the 3 Ways to Become a Better Tester in 2024.

This is a valuable reflection from Mihaela Sfat on what it takes to take on a leadership role in testing and how to navigate that.

Moreover, Russell Uzal describes his view of The Role of the QA Lead in the Context of Scrum Teams.

Maria Golubeva shares with us several practical tips on the good approach to test automation, using Cypress tests as examples.

However, be aware of A Boatload Of Red Flags In Testing described by Rowan Powell.

Ash Winter explains why it's worth investing more in preparation and testability before automating tests.

It's also important to remember about The risk of changing your tests, as Roshan Manjushree Adhikari explains.

Rodrigo Matola shares his vision on how to make sure that test automation goes hand-in-hand with feature implementation.

That said, Érick Souza asks: Does 100% test coverage mean full assurance of quality?

Here's some practical advice from Google engineers, Andrew Trenk and Dillon Bly, on testing without mocks.

However, Peter Merrill shares his point of view on mocking in order to Balance Quality and Efficiency.

I like Noemi Ferrera's take on when to stop testing, measured by the cost.

But sometimes you need to Think Like A Tester And Test For The Impossible, as Wayne Roseberry points out.

If you're curious about how to implement API tests in the BDD fashion with Serenity, Rashad Chowdhury wrote a helpful guide.

But keep in mind Fabio Dias's advice on BDD and Gherkin — You are doing it wrong!

Christine Pinto prepared a fine overview with examples of using AI to enhance test automation with Playwright.

Also, Adrian Maciuc wrote a great guide to various ways of Debugging with Playwright.

If you want to learn more about property-based testing, João Coelho shows how to use the fast-check tool for that.

There are plenty of suggestions on tools that allow reproducing issues and sharing them with devs for easier debugging.

Alex Khvastovich recorded a decent, 13-minute tutorial to Playwright's Test Generator capabilities.

Also, did you know you can Turn Playwright tests into Artillery Load Tests? Learn how with Jarad Saunders.

Having worked at Google, Facebook, and now Apple, Simon Stewart shares tons of insights into test automation and its challenges. Kudos to Nikolay Advolodkin for hosting this interview.

Like a cat and dog... 😂

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