Welcome to the 276th issue!

Have you heard of Stagehand?

It's a new open-source AI automation framework that operates on just three main commands and leverages Playwright to inspect and execute actions in the browser.

If you want to learn more, Yatheendra Sai wrote a helpful article describing it in more detail.

It's good to see more such solutions emerging. I'm convinced we may hear more about them in the future.

Happy testing! 🙂

Dawid Dylowicz

Demi Van Malcot shares several helpful tips on how to properly integrate QA people and processes into a product engineering team.

Moreover, James Kip explains Why Traditional SDET Interviews Are Broken (and How to Fix Them) in the first place.

Following the first part, Gil Zilberfeld continues sharing good advice on test planning, focusing specifically on what it should include.

Also, Jayateerth Katti explains why Zero bugs doesn't mean you are lazy. It shows your guardrails worked.

Jitesh Gosai correctly points out that there's more to achieving software quality than just testing and advises on what to focus on as well.

Similarly, Sarat Ramineni wrote a good article about Quantity ≠ Quality: Why More Testing Won't Save Your Product.

AI is all around software engineering, and we have to accept it and adapt our testing and quality practices to it. Wendy Erdheim-Poch shares some good advice on that.

Furthermore, Jeff Nyman writes about Quality Assurance for Society in the age of AI.

A good reminder from George Ukkuru about why it's important to highlight challenges effectively while exploring and testing the system.

On the other hand, Alessandra Moreira mentions some of The Words That Break Software.

How would you test the integration between the UI and API of the web app? Peyman Iravani shows extensive examples of achieving that in JavaScript.

Furthermore, Peyman also wrote about Advanced JavaScript Testing Strategies for Modern Web Applications.

If you're starting your journey with test automation, Mona M. Abd El-Rahman gives several good tips on how to do it effectively, step by step.

Choosing a test framework isn't only about comparing features. Benjamin Bischoff explains that other factors should be taken into account, such as team expertise, documentation, culture, and maintenance.

Also, What If Your Tests Healed Themselves Overnight? Harpreet Sohal shares how it could be achieved.

While testing APIs, you may encounter various HTTP codes. Elena Voevodkina explains why using the right ones matters for clarity, automation, and future maintenance.

Kishor Munot demonstrates how to automatically measure website performance metrics using two open-source tools — Cypress and Lighthouse from Google. You can also read the first part, which explains how Lighthouse works.

Need to test your web app for accessibility? Yevhenii Otsevych proposes a new way of doing it based on the Page Object Model by using the open-source library he created — axe-playwright-report.

Also, Arthur Tee Seng Tuan wrote a helpful guide to Performance Testing with Playwright and Artillery.

Debbie O'Brien announces that Playwright 1.53 is here and it brings some exciting features and improvements to trace viewer, HTML reporter, assertions and more.

Similarly, Shivam Bharadwaj shares What's New in Playwright v1.53.0.

Siarhei Shukalovich has an interesting point of view on how to enhance your Playwright test tracing and debugging.

Also, Debbie O'Brien describes the new way of Debugging Playwright Tests with AI: A Smarter, Faster Workflow.

Want to learn more about AI in testing but don't know where to start? Keith Klain collected several recommendations in the form of books and other resources.

Alex Khvastovich has been working on a helpful introductory course for Playwright. Here's a 20-minute overview of implementing visual tests, followed by Part 7 about Accessibility Testing.

QA jokes... 😂

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