Welcome to the 253rd issue!

Oh my, time flies!

It's hard to believe this week marks 5 years since I sent out the first issue at the beginning of 2020.

Little did I know I would consistently show up every week, searching for the best news and delivering it to your inbox.

My only goal has always been to focus on the next week — that's it.

And here we are, over 250 weeks later!

It's been an extremely rewarding journey so far and I'm deeply thankful that you're part of it.

So cheers to that, and happy testing to you! 🙂

Dawid Dylowicz

This time, Michael Bolton shares great insights into what answers we should provide to the business when testing. This is followed by a good explanation in Part 5: Intention, Discipline, Testability, Realization.

In relation to that, Ravisuriya Eswara is asks and answers: Is Software Testing a Cost to Business?

This is a very good, thought-provoking article by Cristiano Caetano, contemplating the hypothetical evolution of the software tester's role in the age of AI.

Dmytro Stekanov makes a good point that testers who better understand product management can be more effective in their roles.

Also, Gil Zilberfeld explains why Pairing to the Extreme is beneficial not only for developers, but also for testers.

In pursuit of new influences a tester can make within the company, Jesper Ottosen explores how we can evolve our roles to support the legal and compliance stakeholders. Jesper also wrote more about Having Smarter Compliance Interactions.

Good suggestion! Alishba Mumtaz describes the benefits of testing for developers in a logical and pragmatic way.

Moreover, Mike Harris simply explains how Using recognised techniques to create tests gives teams advantages.

Christopher Enitan shares some practical guidelines for holding the team accountable for maintaining healthy test suites.

And, to run the tests properly, you may want to know about Continuous Integration (CI) and Continuous Delivery (CD) pipelines for software testers, as explained by Ady Stokes.

Working with LLM-based apps? Farzad Shojaei shows examples of how to approach testing them.

Furthermore, Sarah Packowski wrote a great article stating that Trying to fully automate evaluation of deployed RAG solutions is risky.

Designing and running performance tests is just half of the success. It's equally important to have the right reporting and monitoring in place. And this is what M M Kishore outlines in this article.

Anji Boddupally gives several good examples of enhancing your functional test automation suite with security-oriented checks.

The test pyramid is often portrayed as a go-to test strategy, but how does it work in practice? Carlos Chaves has some great insights into why it depends on your system's architecture system.

Want to run your Playwright tests faster? Vijay Kumar shows how to split them up into smaller groups and run in parallel on CI.

Additionally, Deep Shah wrote a good overview of using Hard Assertion & Soft Assertion in Playwright.

If you want to write your API tests in a BBD style using a modern test framework, you might be interested in this guide to Cypress with Cucumber by Ravi Gajanan Gaygol.

Furthermore, Uros Simic has some tips for Cypress Reusability: Custom Commands, BaseUrl and POM.

It turns out you can use Cypress for web app performance testing, too. How? Valiantsin Lutchanka created a handy plugin cypress-performance that measures and asserts web performance metrics.

When starting a new project, you may face an overwhelming choice of tools. Deniz İdil Onat gives some practical advice on how to approach the evaluation process.

Have you heard of Context-Driven Testing? In this 25-minute video, Alan Richardson gives an insightful overview of this school of testing.

Have you seen a Heisenbug?... 😅

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