Welcome to the 259th issue!

Three weeks ago, I highlighted what testers think about AI.

Today, I want to share with you more insights about the adoption of AI in testing:

• How many of you use GitHub Copilot?
• Any idea how to implement AI in regression testing?

I also liked Bas Dijkstra's approach to setting his own Terms and conditions for using AI.

Happy testing! 🙂

Dawid Dylowicz

Continuing a great series of articles explaining the foundations of testing in simple terms, Mona M. Abd El-Rahman gives an overview of API testing. And it's followed by A Comprehensive Guide To Structure and Anatomy of an API.

This is an interesting thread on Reddit about the pros and cons of working as a tester at corporations and startups.

How do you approach testing specific features? Mirek Długosz lists a few things to consider when making the decision.

A great complimentary read to that is Joep Schuurkes' advice on Optimizing for moments of discovery.

Sometimes, developers and testers have different views on software development. Lena Pejgan Nyström offers a few tips on how to make the best out of this collaboration.

Should we just test in production? Denis Stebunov shares an interesting point of view on test environments and solutions that enable testing in production.

Struggling with slow end-to-end tests? Roy Klein gives a few practical tips on how to speed up the execution on CI.

Also, How does unit testing work in your company?

Irfan Mujagić shows examples of four approaches to control test execution based on the environment.

In relation to that, Daniel Draper explains why Testing is more about setup than scripts.

Do you know about Lambda expressions in Java? Govinda Solanki provides a few handy examples of using them to write more effective test automation code.

If you're curious about testing blockchain apps, Thanasornsawan Varathanamongkolchai gives a thorough overview of automation using Hardhat.

Santiago Mattiauda wrote a great, comprehensive overview of various types of tests for Android apps with examples.

Furthermore, Isaac Lee shares another part about Automating UI change verification with Android Compose Screenshot Testing.

Do you want to make your Playwright test configuration more flexible? Kostiantyn Teltov shows a few tricks to achieve that.

Also, Butch Mayhew wrote a fine guide to Playwright-Cli-Select For Quick Targeted Test Runs via CLI.

AI enables us to get more insights from test reports. Matthew Poulton-White tested out a few models and shared the results.

Similarly, Razvan Vancea explored AI-powered Playwright Test Reporting with Testbeats, followed by Thananjayan Rajasekaran demonstrating the well-known Report Portal with Playwright.

Have you heard of the Robot Framework? It's a fairly popular tool for streamlining test automation and here you can read testers' opinions about it.

Cypress is known for its extendability via plugins. Sebastian Clavijo Suero created an insightful list describing the most handy ones.

Sebastian also continues the series of articles about The Test Drama: Cypress vs Playwright — Control Your Tests: Annotations & Group Tests.

Maxwell Nyamunda gives a practical overview of Playwright's visual testing feature.

Moreover, Debbie O'Brien has a helpful tip on Playwright Assertions: Avoid Race Conditions with This Simple Fix!

An easy bug... 😂

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