Welcome to the 201st issue, and happy new year!

Let's start it with a reflection:

What QA knowledge did you learn in 2023?

There are some common, as well as unexpected learnings in this thread.

But when it comes to me, I've learned a ton from curating all the great content over the past year.

I hope you did, too.

Happy testing in 2024! 🙂

Dawid Dylowicz

Gaurav Singh wrote an excellent article about navigating different dev-to-QA ratios and how to solve some common problems with them.

Furthermore, Dennis Martinez explains How Testers Help Developers Elevate Their Productivity.

If you're wondering what types of test techniques you can use to validate products in Agile testing, Julia Kocbek wrote a great overview.

Additionally, Hannah Son emphasises the importance of Acceptance Criteria in Agile Testing.

Testers deliver the most value when they communicate about their findings early. Here's a good reminder from Callum Akehurst-Ryan on why we should be proactive in our efforts.

Justas Laužadis lists out the criteria for judging how much we can trust AI and uses them to highlight the importance of testing it.

Fri Rasyidi describes several testing techniques that can help you measure your test coverage and assess whether something is tested enough.

It's also important to remember about The Real Requirements, as Michael Bolton reminds us.

I liked Stuart Thomas's take on the definition of quality based on examples of two different problems with apps.

There are some great principles and pieces of advice on how to do test automation properly in this list created by John Gluck.

Gleb Bahmutov shows us why we should avoid using auto-generated test IDs in web elements with some comprehensive examples.

If you're unsure about the benefits of testing, especially at the unit level, Daniel Draper has a good explanation.

Additionally, Google engineers Shiva Garg and Francois Aube have great advice on Letting Code Speak for Itself.

While test automation can bring great benefits to testing at scale, Kemal Taskin reminds us that it also comes at the cost of maintenance and advises how to minimise that.

Also, Ivy Murphy explains why The Automation Utopia is a Mirage.

Playwright is a versatile tool and Andrey Enin shows how you can use it to validate contracts of your APIs.

Moreover, Kostiantyn Teltov explains the Controller and action layer concepts in API test design.

This article by Jon Reid has some great practical advice on speeding up your iOS test setup in XCode.

Furthermore, Emin Deniz wrote a comprehensive guide on iOS UI Testing with Deep Links.

With the rise of modern test tools and frameworks, one may wonder whether it's time for Selenium to go away. This thread contains a lot of fair answers.

On that note, Butch Mayhew asks: Will Playwright Replace Cypress?

Harshit Daftary shares a very interesting approach to using AI to automatically debug failed tests and speed up the investigation process.

Wondering which AI tools can help you with testing? Daniel Knott recorded another great overview.

If you're looking for advice on building and growing your career in testing, Anna Patterson and Nikolay Advolodkin have got you covered in this comprehensive, one-hour discussion.

First day as a new QA Engineer be like... 🤣

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