Welcome to the 244th issue!

Looking for ways to become a better tester?

This week, I want to highlight two great articles with references and advice:

• 99 essential resources to help software testers by Rahul Parwal
• How to improve your Software Testing skills by Yogesh Khairnar

Happy learning! 🙂

Dawid Dylowicz

With the big push towards automation and recent breakthroughs in AI, Cristiano Caetano wonders where we are on the journey towards autonomous testing.

It's well complemented by Cristiano's thoughts on The rise of the hybrid tester in the context of AI.

Where's testing going next? Maaret Pyhäjärvi shares a vision across four themes: automation, opportunity cost, social and AI.

Have you encountered a bug that you can't reproduce? James Wadley calls them Heisenbugs and advises on what to do with them.

At the same time, Callum Akehurst-Ryan wrote a good article: Is it really an edge case?.

Gaurav Singh explains the possible career paths in testing and advises on which tech and soft skills you should develop.

Similarly, Mariam Sargsyan shares the experience of Redefining My Role in Testing: A Journey Through Industry Noise.

There's some great advice from Keith Klain on how to keep your test team performing. It's valuable for both managers as well as individual contributors.

Furthermore, Heemeng Foo shares a few good points on What I look for in a Test Engineer and Mykhaylo-Ivan Filipenko explains Why Most QA Interviews Suck.

Reiterating the message I featured last week, this time it's Michael Bolton who explains the important difference between testing and quality.

This is further emphasised by Nicola Lindgren's take on The Importance of Perception in Testing, as well as Maaike Brinkhof's interesting story of Neutral Quality.

Or is it? Ville Rytinki explains the pros and cons of such an approach and why collaboration between testers and developers is important.

Ville also wrote about the challenges with Over-reliance on E2E testing.

I truly enjoyed Rob Kokochak's take on the importance of understanding the "why" of testing.

Following that, Mohammad Faisal Khatri shares a high-level Five Point Plan To Start Automation Testing.

Julia Kocbek gives several valuable pieces of advice on the effective approach and implementation of test automation.

Also, Michael Scotto wrote a good overview of Using the Testing Trophy heuristic.

While AI proves to be a great assistant in code development and testing, it's risky to fully rely on it. Mohammad Azam explains why.

One of the ways to partially address that could be Enhancing Test Effectiveness with Mutation Testing, as João Coelho outlines.

Wondering how object-oriented programming principles can be applied in test automation? Gulshan Nadaph has a few ideas.

Robot Framework is a versatile, open-source automation framework that can be used with many popular test tools. Ahmad Azeri Chandra Bhuana demonstrates how to set it up for testing Android apps.

Nikita Filonov wrote a comprehensive guide to setting up a test automation framework with good practices using Playwright and Allure Report.

And that's not all — Nikita also shows how to Write API automation tests in TypeScript with Playwright.

Mirek Długosz gives an honest review of the recently released book titled Software Testing Strategies.

In this short video, Daniel Knott warns against 14 different approaches in testing that can put your projects at risk.

Looking to change jobs? In 10 minutes, Alex Khvastovich gives valuable advice on what to pay attention to in your resume and shows an example of a good CV.

10 signs you've been a software tester for too long... 😂

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