Welcome to the 281st issue!

Jason Huggins, the creator of Selenium and Appium, has recently announced a new project — Vibium.

It will be a completely new, open-source, AI-native test framework, aimed as a successor to Selenium, which sounds exciting.

I felt it was just a matter of time for something like that to appear. So I'm glad to see a commitment from someone as experienced as Jason.

We still need to wait for more details, but I hope it works out!

Happy testing! 🙂

Dawid Dylowicz

There's very good advice from Daria Kotelenets on what to do to improve quality processes and outcomes in your team.

Similarly, Marina Jordão suggests: Want Strategic QA? Start with What Every Great Company Has: Core Values

What should you focus on while testing? Sam White suggests a mnemonic to remember the minimum expectations we should have as testers.

Moreover, Niraj Subedi reminds us about The QA Triangle of Doom: Speed vs Cost vs Quality: Pick Two (If You're Lucky) and advises how to solve it.

Sam Farndale and Gina Chelton share an inspiring story of redefining test strategy across the company, explaining their choices.

Also, Nureko Wibowo shares about How I Transformed QA with Risk Management and How Our QA Team Learned to Tame Uncertainty and the lessons learned.

Want to know what is important in shift-left testing? I liked this pragmatic explanation by Carlos Chaves, emphasising the tester's role.

In a related article, Vikram Mahendrakar demonstrates How API Testing Shifted Quality Left in their case.

It's a catchy statement! I mean, who likes bugs? Charukshi Wijesinghe expresses her vision on why it actually makes sense.

Furthermore, Paul Grizzaffi shares some interesting thoughts: You Broke Me? Why We Release With Bugs.

Using AI to help you with testing? James Kip shares some valuable tips based on his experience with fixing tests.

Have you heard that Chrome DevTools gained support for AI assistance? Well, now you have, and Alan Richardson has kindly tested this feature out and presented it to us.

Mirek Długosz describes in detail the process and lessons learned of building an automated framework that runs tests at scale.

Automated tests should generally be deterministic and repeatable. But sometimes it might be good to introduce some randomness, too. Daniel Haimov gives some interesting examples.

On top of that, Farzad Shojaei shares examples of why SQA is responsible for writing a secure code.

If you're testing mobile apps created with Flutter, Panduka Wijekoon gives an overview of the Patrol test framework, including examples of setting it up and running.

Sometimes beforeAll is not enough. Vitaliy Potapov shares some handy tips on making some Playwright test setups easier with a custom global cache.

Irfan Mujagić describes the waitForRequest function in Playwright that can make your UI tests more reliable thanks to the awareness of API call processing.

There are plenty of resources about using AI for testing. But what about testing AI itself? This is a fascinating conversation between Alex Khvastovich and Igor Dorovskikh about that.

If you're using Playwright for testing, you might be interested in this informative, 16-minute overview of the latest features by Joan Esquivel Montero.

That's one way to solve a 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