Welcome to the 236th issue!

Have you heard of Awesome Test Automation?

It's an open-source collection of great resources on test automation, such as tools, practices, and examples in many popular programming languages.

Kudos to Dmytro Zharii and Mykhailo Poliarush for maintaining it.

Happy testing! 🙂

PS. Thanks to those who shared some resources on testing in machine learning last week!

Dawid Dylowicz

It's a good question. Maaret Pyhäjärvi highlights the importance of understanding DevOps practices, test environments and CI/CD management for testers.

Also, Jesper Ottosen advises to Throw a Disaster Party and learn how your systems handle disaster recovery.

Writing a lot of test cases can sometimes become a daunting experience. Cassandra H. Leung shares how to make it more interesting and beneficial.

Furthermore, Wayne Roseberry wrote a great overview of Different Approaches To Test Cases.

Cristiano Caetano correctly points out that the quality of requirements plays a key role in effective testing, especially in the age of AI.

On the other hand, Roman Lagutin gives some practical tips on How to do QA for a service missing requirements.

Prateek Mishra proposes a method to prioritise test cases for regression testing using three attributes: Historical Failure Score, Test Case Complexity and Defect Exposure Capability.

In relation to that, Vitaly Sharovatov does some QA myth busting: more testing means better quality.

In case it wasn't clear, Uros Simic makes a good point on what makes BDD effective and why testing is just a part of it.

Similarly, Abhijeet Chavan describes Common Anti-Patterns in Cucumber: How to Avoid Them.

Wondering how to test LLM-powered Chatbots? Adi Adrian wrote a handy, automated solution for that.

Arek Frankowski shows a few examples of how to improve test design with SOLID principles and other good programming practices.

However, remember Why reaching 100% Code Coverage must NOT be your testing goal (with examples in C#), as Davide Bellone points out.

The problem with test automation is that it's not always implemented alongside the feature code. Shivam Bharadwaj explains how writing dummy tests helped him and the team close that gap.

Learning from a previously failed test automation attempt, Heitor Colangelo shares an insightful overview of a new approach they took to do end-to-end testing of mobile apps.

Speaking of mobile, you may also want to explore The Robot Testing Pattern described by Kacper Rubaszewski.

Is the inverted test pyramid an antipattern? Gil Zilberfeld explains when and why it might be applied in such a form.

As Postman has grown into an API testing solution focused primarily on businesses, testers and smaller teams are looking for more lightweight GUI solutions. Here's what the testing community recommends to check out instead.

Some of the JavaScript-based test frameworks set test timeout by default. Josh Grant argues it may cause unnecessary test failures and frustration for teams.

There are many ways to locate elements using Playwright. However, Nočnica Mellifera advises using the ones that are the closest representation from the user's perspective in order to find accessibility issues.

Moreover, Thananjayan Rajasekaran wrote a handy guide on Optimizing Database Integration in Playwright.

This is a good example by Gleb Bahmutov of how to properly use the network interception feature in Cypress.

If you need to test AWS cloud and serverless solutions, Igor Venturelli shows how to make it easy using LocalStack.

Testing Android apps? Ryan Wong explains the challenge of the absent id attributes in Jetpack Compose and shows how to overcome that with the .testTag() feature.

Joan Esquivel Montero highlights the differences between real browsers and browser engines often used in test automation, based on the original talk by David Burns.

This is a great talk by Daniel Knott about the importance of values for software testers on both personal and professional levels.

Evil "bugs"... 😅

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