Welcome to the 268th issue!

Quality is hard to measure.

But the activities impacting quality can be measured, such as development practices, technical debt or test coverage.

That's where QE Score comes in.

Simon Champenois created it to pragmatically collect and track metrics in one place.

To learn more, check out Simon's article about Quality Engineering, Quantified: What Your QE Score Really Means.

Happy testing! 🙂

Dawid Dylowicz

If you don't know what exploratory testing is about, this is a clear introductory overview by Mona M. Abd El-Rahman.

Do you review requirements? Hanisha Arora explains why it's important in shift-left testing and how to do it well.

Furthermore, Aya Akl advises to Prioritize What Matters: How Risk-Based Testing Improves Product Quality.

There's no denying that AI is changing software development. Filip Hric shares five predictions on how it will impact software testing.

At the same time, Alessandra Moreira points out that Fast Isn't Free when it comes to AI solutions.

Vladimir Josifoski has some good advice on how to attain specific ways of thinking and questioning to become a better tester.

Also, here's what the community says: What do you think are key skills to have as a QA?

This is the first of a few other Reddit threads I'm featuring in this issue. It's a great discussion about different approaches to improve the work and collaboration of your team.

In relation to that, Maaret Pyhäjärvi wrote a short piece explaining the importance of Resultful Testing.

Harmeet Singh thoroughly explains what to take into account for front-end performance testing and shows examples of doing it with Cypress and Playwright.

It's an insightful discussion with various points of view on how to approach end-to-end testing, which isn't always straightforward since it may depend on project needs, architecture and even beliefs of the people implementing them.

What is the right test automation strategy? Brijendra Singh points out the pros and cons of the test pyramid and describes the alternatives.

Philip Riecks has some good tips for those of you who are using Java and testing Spring Boot applications.

I agree with Niraj Subedi that being able to read and review code as a tester before it gets shipped can lead to better quality outcomes.

Debbie O'Brien explains how to use ESLint in Playwright tests to spot unexpected code flaws.

You can also explore the ESLint, Prettier & Pre-Commit Setup for Playwright.

Running Cypress tests in parallel? It's likely that you're receiving multiple test results. David Ingraham shows a handy solution to merge all of them into one report on CI.

Tooba Munir gives an overview of the Network functionality in Chrome DevTools that can help you test specific use cases of your web app by overriding API responses.

Furthermore, Raymond Saba and Giuseppe Donati share a story behind Tailor-made browser extensions for increased testing efficiency.

Argo Triwidodo describes how they used Selenium Grid Scaler to dynamically scale test infrastructure depending on Selenium test execution needs.

What do you use for test case management? Someone dissatisfied with the process is seeking advice from fellow testers.

Do you know Bruno? It's a simple, free API client, which Alan Richardson describes in this 24-minute video.

Moreover, Dheeraj Gambhir put together a comparison of Bruno vs Postman: Which API Client Should You Choose?

In 35 minutes, Alex Khvastovich demonstrates how to use Playwright MCP with GitHub Copilot to create automated tests.

Similarly, Denis Skvortsov wrote about the Practical use of Cursor and MCP Playwright in test automation.

QA Archetypes... 😂

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