Welcome to the 258th issue!

Some people fear that AI will replace software engineers, including testers.

However, Tim O'Reilly doesn't think it's the end of programming.

It's The End of Programming as We Know It.

In short, "AI will not replace programmers, but it will transform their jobs."

But naturally, we'll need to adapt. So keep learning and exploring.

Happy testing! 🙂

Dawid Dylowicz

If you want to learn the foundations of accessibility testing, Mona M. Abd El-Rahman put together a good introductory guide that covers the basics and lists several tools to explore.

Daniel Terhorst-North takes us on a thought-provoking journey through the possible paths of building software, which involves balancing quality with speed.

Furthermore, Lena Pejgan Nyström gives an overview of Getting intentional with heuristics in software testing.

Aya Akl shares several tips on what to do and not do when it comes to testing mobile apps. And there's more about usability and user experience in the second part.

Do you know what skills you should be developing as a test engineer? Hannah Son wrote an extensive article explaining the importance of T-shaped growth with examples.

Bug bashes are a great way to come together and test the product internally. Parveen Khan explains how to organise them.

Automated tests often serve as documentation and reference for expected behaviour. Stefano Alvares points out why it's important to do the test naming right in that context.

Wondering how to test systems that behave differently based on feature flags? Sravanti Tatiraju describes several test automation strategies with examples.

Gil Zilberfeld shares some interesting thoughts on how we should perceive automated tests' role in software development.

Are you familiar with snapshot testing (the non-visual one)? Alex Hamer shares his thoughts on why it might not be the best approach and what to do instead.

Similarly, Tomer Ben-Dror shares an opinion on why Integration Tests belong to the Past.

Continuing the insightful series of articles on contract testing, this time Eleonora Belova shows how to set up Pact Broker on CI.

To simplify test management, Felipe de Campos came up with the idea of writing Playwright tests in YAML. You can learn more about it in the following part about Assertion and Code Evaluation in Our YAML Testing Framework.

Bas Dijkstra shows how he recently extended the test coverage for the open-source RestAssured.Net library with mutation tests, using Stryker Mutator.

With the latest release of Playwright's 1.50 version, you can now copy API requests as Playwright code, which is a very handy feature if you're writing API tests. Butch Mayhew shows how to use it.

Curious about the experience of getting started with Cypress and Playwright? Sebastian Clavijo Suero wrote an extensive overview, sharing insights from his experiments.

Furthermore, Vadym Nastoiashchyi shares an overview of JavaScript UI Test Automation Frameworks — latest updates in 2025.

This time, Karthik K.K. is trying out the new GitHub Copilot Edits feature to generate Playwright tests with AI.

Preparing for an ISTQB exam? Chamila Ambahera put together a collection of short videos that explain the key concepts in a simple way.

In this 11-minute recording, Alex Khvastovich brings up several points on what makes test automation hard. And it isn't writing tests!

Fixing flaky tests... 😂

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