Welcome to the 168th issue!

As AI continues to play an increasingly important role, it raises questions about testing its behaviour and accuracy.

Recently, I found an immersive, thought-provoking article on this topic:

AI Needs Testing by Jason Arbon.

It lays out the vision of AI development and explores the challenges we may face testing it. Well worth the read.

Happy testing! 🙂

Dawid Dylowicz

Acsah Mathew wrote a practical guide to Context-Driven Testing, including examples from her work.

Moreover, James Thomas is asking: Am I Wrong? (About Exploratory Testing).

Testers and developers need to work together to increase the chances of successful product delivery and quality work. Christian Nissen gives a few pieces of advice on how to achieve that.

However, sometimes you may face a situation where Whenever bugs come into production I feel depressed.

Asking questions is an important part of the tester's role. Joep Schuurkes shares some of his preferred examples.

Also, Snehal Salunke explains: Is software testing easy?

In the final part of the series, Alejandro Sanchez Giraldo gives an overview of a framework for optimised quality.

Similarly, Bogdan Spuze advocates for Quality before anything by describing team members' roles in testing.

Bryan Mahdavikhia shares general advice regarding mocking in test automation and shows an example in Python with Django.

Furthermore, Wellynton Ribeiro Moreno demonstrates How to improve automated test accuracy using data-test-id.

Daniel Delimata explains the benefits of using the Page Object Model and gives examples of other patterns used in test automation.

Note: If you can't access the full article, open it in a private tab or another browser.

Login tests are often used as examples for test automation because they're simple. But what if there's two-factor authentication involved? Guilherme Pinheiro wrote a comprehensive guide explaining the test design for such cases using Pytest.

There's no denying that software quality and testability start with good architectural design. John Gluck advises keeping test data management in mind when doing so.

I assume you have all had a chance to learn about ChatGPT's capabilities so far. But what about other AI-based tools? Victor Ayomipo prepared a great overview.

Also, Dennis Martinez describes in detail how to Supercharge Your Test Automation Using GitHub Copilot.

Robolectric is a helpful tool for automating Android tests. Romman Sabbir uses examples to demonstrate what it can do.

If you're looking for practical applications of ChatGPT, here's an interesting thread on Reddit.

You may also want to check out another thread on Getting onboard with ChatGPT for front-end testing.

Want to improve the debugging process of your Playwright tests? Madeline Caples shows how to use test steps for that.

Additionally, Butch Mayhew wrote a helpful guide on Handling Headers and Authentication in Playwright.

Zhimin Zhan gives a few reasons why Selenium should always be considered for test automation over other, paid solutions.

Also, in response to my comment from the 166th issue, Zhimin is asking: "Cucumber is Dying", what did we learn?.

Note: If you can't access the full article, open it in a private tab or another browser.

Matt Heusser started a series of short videos sharing secrets of software testing. You can also listen to advice #2 and #3.

In a 38-minute talk, David Burns explains why differences between browsers and environments matter in testing.

Always testing... 😂

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