Welcome to the 138th issue!

Over the past years, we've seen a lot of new open-source tools for testing web apps.

Ever wondered how they really compare? Here's the answer:

What a Google Search Can't Tell You About These JS Testing Frameworks.

Thanks Daniel Caldas for this fair, detailed, data-based overview of the six most popular tools.

Happy weekend and happy testing! 🙂

Dawid Dylowicz

Accessibility testing is becoming an important part of test strategy in many companies. Małgorzata Czuluk and Anna Borgosz give a comprehensive overview of why it's important and how we can support the testing process.

New to exploratory testing? In this Reddit thread, a lot of people share tips on what to do and not to do.

Furthermore, Mārtiņš Belte wrote a good article about Approaching the quality process with experience-based and exploratory testing.

Venkat Ramakrishnan shares some interesting insights into working with machine learning and the ways we can test it.

Whole-team approach to quality is one of the main agile testing principles. Ryan Craven shares his experience of joining a team with that mindset and what impact it had.

On top of that, you might be interested in implementing some Metrics for Testing — Guide to Quality Assurance as Aroni Das explains.

Mihaela Sfat shares her story of becoming a QA Lead and what she learned from that journey.

And if you're looking for new opportunities, Melissa Fisher put together a few great tips on CV writing for software testers.

Moreover, Nicola Lindgren summarised four helpful Software Testing Job Sites.

Looking to begin your journey with test automation? This advice from Ben Dowen might come in handy.

Also, Maciej Rojek has got you covered if you don't know where to test your automation skills.

Here's a practical guide to two open-source tools — Testcontainers and Zerocode — that can help you with testing the integration of data streaming systems. Examples by Redpanda Data.

Test automation isn't easy. But sometimes you may find some quick wins that can significantly improve your tests. Dennis Martinez explains how.

Do you know how advanced and mature your test automation practices are? Johanna South created a handy, four-level assessment for your convenience.

Wait, but isn't it an antipattern? Well, it is. But every rule has its exceptions. And if you find yourself in such a situation, follow Gleb Bahmutov's advice on doing it right using Cypress as an example.

Speaking of test coupling, Sajitha Pathirana answers the question: Do you think it is good to have tests under the development project?.

The day has come! After years of waiting, Cypress 10.8 finally brings support for Safari! It's still an experimental feature but you can enable it easily. This guide by Kailash Pathak shows how.

If you're interested in monitoring and getting notified when your tests turn red, Sai Anudeep Adimulapu shows a simple example of setting up and using Test Results Reporter for that.

With so many types of elements in web apps, it's sometimes hard to keep track of their names. Shoeib Shargo suggests a structured naming convention for variables and shares a handy cheat sheet for reference.

System thinking has proven to be helpful in software engineering. Mike Harris shares what he learned about it so far and recommends a few books to explore.

If you wonder what the value of unit tests is, watch this 48-minute tutorial by Gil Zilberfeld that shows how they can support code refactoring.

What a job opportunity... 😂

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