Welcome to the 188th issue!

Despite its popularity, Behaviour-Driven Development is an often misused and even disliked practice.

But why?

Well, check out this discussion on Reddit, which started with a question:

How is BDD used in your team?

We can find many insights there from people sharing their opinions and experiences.

So enjoy the read, and happy testing!

Dawid Dylowicz

If you're looking for the meaning of software testing terms, look no further! Luc Gagan created a super handy Software Testing Glossary.

In that context, Callum Akehurst-Ryan asks and explains: Is Manual Testing a Dirty Word?

Mas Kono and Paul Grizzaffi suggest a new metric using test case points to track testing progress more effectively by prioritising the most important ones.

Furthermore, Ihan Dilnath emphasises that Tests that validate business value are tests that add business value.

Wondering how to effectively use AI chatbots to help you in your day-to-day work? Jason Arbon shares some great advice.

Similarly, Zubair Usman Paracha gives a few points on how to do Bug Hunting with GPT: Tips, Tricks, and Prompts.

Someone is looking for advice on what they can do to handle testing several streams of work where the dev-to-tester ratio is high, and the community comes with some helpful suggestions.

One of them is a recent Mike Harris' article that greatly explains How a lone tester can work across teams.

You're probably familiar with the Page Object Model used for structuring tests of front-end apps. What if we used a similar approach for APIs? Khaled Arfaoui shows how.

Moreover, Anji Boddupally wrote a solid overview of Design Patterns in Test Automation.

Is your test suite efficient? Sander van Beek showcases an experiment on unveiling redundant tests through mutation testing, sharing both the process and findings.

Also, here's an interesting discussion: Is repetition unavoidable in E2E tests?

Here's a hands-on example by Christian Ascone proving that high code coverage alone doesn't equate to thorough or effective testing.

If you experience flaky tests, Cerosh Jacob has some helpful advice on what to do with examples in Playwright.

Additionally, Giuseppe Donati shows some good End-to-end tests retry strategies, and Mike Harris explains why Automated tests do not have to be flaky.

If you want to learn what types of tests are and aren't generally considered good candidates for automation, Lesia Topol created a handy overview with a cheat sheet.

In relation to that, Janet Gregory and Lisa Crispin wrote a great article about the Test Automation Pyramid.

Setting up modern tools like k6 is easy following the official documentation. But it gets challenging to add a custom setup, such as your own node modules. Felicia Walker shows how to solve some of these challenges.

Cypress has some helpful mocking solutions to aid your testing, such as API response interception. Kailash Pathak describes it in detail.

This is a nice follow-up read to some great advice on improving Playwright test execution speed from the previous week's issue.

Additionally, Kostiantyn Teltov wrote an article about Playwright with .NET. What? Is it useful?

One of the desired solutions in advanced test frameworks is the ability to run a subset of tests based on the affected code changes. Gleb Bahmutov shows a great way of achieving that in Cypress.

This bug won't age well... 🤣

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