Welcome to the 263rd issue!

This discussion blew up — Is it common for devs to dislike QA?

While in some environments it may still occur, most people haven't experienced it on a regular basis, only as an exception.

Regardless, there's some good advice on how to deal with it.

So, happy testing! 🙂

Dawid Dylowicz

Great reflections, lessons learned, and advice from Alessandra Moreira — an experienced Director of Quality Engineering — on how to work towards the quality leadership role.

Similarly, Oliver Martin-Hirsch shares about The Leap to Leadership: An honest experience from an anxious SDET.

Have you ever tried pair testing? Daria Kotelenets brings up several good arguments on why it's beneficial.

Furthermore, Mona M. Abd El-Rahman wrote about Debugging 101: A Beginner's Guide for Software Testers focused on web and mobile apps.

Kostiantyn Teltov explains several types of validation and verification practices we can put in place during different stages of the software development lifecycle.

Moreover, Irfan Mujagić warns against falling into 8 QA Testing Pitfalls: Just Because You Can, Doesn't Mean You Should.

Bart Reits wrote a detailed series of four articles on what it takes to create a quality plan using various approaches. Here you can find Part 2, Part 3 and Part 4.

Also, Aya Akl asks: To QA or not to QA?.

That's a good reminder from Daniel Gold to check your test automation solution and validate whether it does what it really should.

One of the core principles in test automation is to aim for having independent tests. This advice by Alexey Alter-Pesotskiy on how to clean up data between runs is one way to achieve that.

This is an interesting guide explaining how to use your local machine to power LLMs and build a self-healing solution for web application tests.

Just like the title says — Alex Zhukovich explains "the why" and shows "the how" of visual testing on mobile.

Following that, Piero Silvestri shows an example of Using Screenshot Tests in a Compose Multiplatform App.

If you want to improve your test automation strategy with visual tests, Dipen Chavan shows how to implement them using Playwright and other tools.

Also, Debbie O'Brien shares a tip about Handling Visibility in Playwright: getByText vs. getByRole.

Nočnica Mellifera demonstrates how to simplify page objects in the test code with the help of fixtures in Playwright.

Furthermore, Dheeraj Gambhir gives a short overview of using ARIA Snapshot in Playwright.

Looking for an API testing solution? Jolivé Hodehou wrote a detailed guide to setting up and running PactumJS tests in CI.

Under some conditions, you may want to completely stop the test execution. Cypress has just provided an official .stop() feature to achieve that, as Jennifer Shehane explains.

Writing tests in Java? Govinda Solanki listed several helpful language features that you can use in your tests.

James Thomas gives an overview of a book about handling legacy systems — Kill It with Fire: Manage Aging Computer Systems.

Inspired by the same book, Maaike Brinkhof shared interesting thoughts about Sad smoke alarm noises.

If you want to learn about applying a BDD process and writing Cucumber tests with good practices, Gil Zilberfeld explains it all in this thorough recording.

Vibe testing, anyone?... 😂

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