Welcome to the 286th issue!

What's new about Vibium?

After going viral despite not having a working demo, Jason Huggins sheds more light on the project in two recent interviews:

• Revolutionizing Test Automation with Vibium AI — 60 min with Nikolay Advolodkin,
• How Vibium Could Become the Selenium for AI Testing — 30 min with Joe Colantonio.

Both are interesting conversations where we can learn more about Vibium's vision, the relevance of Selenium, and the general state of testing.

Of course, it's an early stage, and despite a small sneak peek, many things can still change. Let's see!

Happy testing! 🙂

Dawid Dylowicz

As someone who believes in pair-programming, I can relate to Matthew Whitaker's article about the benefits of pairing different QA roles.

Shift-right testing practice involves testing and monitoring software post-release. Arik Aharoni gives some good high-level advice on how to do it and the benefits it brings.

This may also be useful When QA Runs Out of Time, as Kevin Konda points out.

Rahul Parwal created an interesting AI-Human collaboration model for testers to identify what areas should be covered by us, and what can be delegated to AI.

Furthermore, Peenaka Wedamulla shares thoughts on How AI Is Redefining the Role of Testers, and Jason Arbon shares insights into What GPT-5 Can't Do.

In the first part of the series, Lena Pejgan Nyström shares a perspective on taking over a QA department, discovering inconsistencies in automation results, and using data and conversations to reveal hidden testing problems.

Moreover, Maria Kedemo shares some interesting thoughts about Learning Faster: Deadlifts, Software Testing and Feedback Loops.

Not an easy question to answer, but definitely an important one. Stuart Day shares a multi-layered definition based on a recent reflection.

Taras Kizlo continues the great series of articles that go into detail about each level of testing. This time, it's about an intriguing topic that not many people talk about — architecture tests.

If you or your team is working on building LLM-based apps, Dr. Ernesto Lee demonstrates how to approach automated testing.

While the Page Object Model is a common test automation design pattern, it's not always done the same way. Here's one implementation example by Đinh Công Cảnh in Python.

Looking for ways to leverage AI in testing? Sam Treweek described an attempt to design a QA model that connects data, tools, and automation to enable smarter, autonomous testing.

Instead of following the test pyramid, Andrew Knight suggests a new approach — a test skyscraper. It emphasises a flexibility that fits the system's needs rather than focusing on the quantity of tests on each level.

In another detailed article, Sławomir Radzymiński gives a comprehensive overview of Chrome DevTools MCP and compares it to Playwright MCP, explaining when to use each.

In search for the best test automation tool, Alan Richardson assessed the current state of popular solutions, compared the shortlisted candidates and gave his verdict. Can you guess which ones are the main contenders?

ARIA Notify API is a new solution provided by browsers for making web content more accessible and Mark Noonan already shows how to test it using Cypress.

Moreover, Adekola Olawale gives practical advice on Fixing Flaky End-to-End Cypress Tests in CI Environments.

Janahan Sivananthamoorthy describes their experience with Artillery for performance testing and explains why they chose it over the other solutions.

Similarly, Irfan Mujagić shares insights into The Smart Way to Begin Performance Testing.

Using k6 for performance testing? In this 25-minute overview, Joan Esquivel Montero shares several tips to make your solution even better.

Vibium-certified... 😂

Thanks for reading!

If you enjoy this newsletter and find it helpful in becoming a better tester, please consider sharing it with others.

Dawid Dylowicz