Welcome to the 272nd issue!

There's a race not only among the commercial AI-powered testing solutions.

The open-source landscape is buzzing too.

How? Well, here's The State of Open-Source AI-Powered Test Automation.

Alex Rodionov shows examples of various tools, categorised as test generators, test runners and test libraries, such as LaVague, Shortest and Alumnium.

Interesting times! 🙂

Dawid Dylowicz

With the new regulation coming to Europe, testing for accessibility is becoming increasingly important. So it's great to see practical advice from Mona M. Abd El-Rahman on how to do that on mobile.

Moreover, Michael Kennedy shares several Empathy lessons for software testers: Preparing for the European Accessibility Act.

Testing the way we've always known it might not apply to AI-based apps. Dick Dowdell describes in detail why and explains how to approach it instead.

Also, there's a good reminder from Sarat Ramineni that Testing isn't dead. It got smarter.

Following last week's article, Jyan Swan shared another interesting point of view on what it is like to be a sole tester in a team.

Furthermore, İlay İnan Ünal has some good insights into Dancing with Requirements: The QA Engineer's Hidden Superpower.

It's hard to set good quality metrics, and so is making them relevant and visible. But Ivan Boklach has some good tips on that.

Xinyu Zhang makes some good points about a tester's evolving role in modern software development and proposes to lean towards Integration Assurance instead.

Similarly, Marina Jordão sheds some light on QA 2.0: As Companies Kill QA, a New Role Is Rising — The Quality Architect.

Wondering how test doubles — such as mocks, stubs and fakes — can help you in testing? Puti Raissa put together a comprehensive guide.

Also, Shubham Sharma explains why Mocking Dependencies in Your E2E Tests is Key to Effective E2E Testing.

You've probably heard about the Page Object Model. But what if we broke down pages into components? Kavita Jadhav explains this approach and its advantages.

Furthermore, Jack Bentley shows examples of Creating a Page Object Model in Cypress.

If you want to learn test automation but are unsure where to start — you're not alone. Someone asked this question on Reddit and got some good advice from the testing community.

And if you wonder what Test-Driven Development is about, Muhammad Hilal Darul Fauzan has put together a comprehensive guide with examples.

We've heard about many test shapes describing test strategy so far: pyramids, honeycombs, trophies... but what about a tower? Jose Maria Flores Zazo shows an interesting point of view.

Michael Bolton shared a very good point on what it takes to properly test our apps from the user's perspective and why tools such as Selenium, Cypress, and Playwright might not fully do that for us.

Playwright has a lot of great built-in features, but do you know about them? Anjali Kulkarni describes some of the powerful, but not necessarily the most obvious ones.

And if you want to test how your web app performs when offline, Irfan Mujagić wrote a helpful guide to Testing Cached Data with Playwright.

Want to start with testing using Selenium? Danyil Antoniuk put together a multiple-part guide to setting it up and running it. You can also read the second and third parts.

One of the main advantages of Playwright is that we can use different languages to implement the tests. For those of you preferring C# and .NET environment, Karthik K.K. highlights the recent official support for XUnit.

While remote work is becoming more common than ever, it's important to know its benefits and challenges, especially in software testing. Daniel Knott explains this in a 14-minute video.

Well, good news… 😂

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