Welcome to the 140th issue!

One question for today (with a lot of interesting answers).

What do you hate the most about being a QA?

To me, it's bugs I can't reproduce. They're a pure time drain! 😅

What about you?

Dawid Dylowicz

You can build a great-looking product, but the perception of its quality won't be so good if it's not usable. Sumithu Rukshitha describes the 7 principles of user experience that you should be mindful of when testing.

Furthermore, you might want to listen to some advice on Creating test cases from user behaviour.

Vaibhav Kalekar describes how the modern responsibilities of testers turn into quality engineering.

You might also be interested in learning: What are your unpopular opinions about QA engineering and software testing?.

Note: If you can't access the full article, simply open it in a private tab.

Monika Krysiak wrote a very detailed overview of security testing with OWASP for software testers.

Moreover, Edina Muminovic explains How Spotify Maintains Security Testing within the Software Development Life Cycle.

And finally, Dheeraj Gambhir advises how to set up CI/CD and Security Testing Integration.

This is a great article on the collaboration between software testers and product managers by Kayvon Ghaffari.

Furthermore, Mike Harris explains why Testing needs to include the needs of internal and external customers.

Since machine learning is becoming a popular solution in more and more companies, it's good to learn what challenges hide there for testers. Fabio Casati gives a great, detailed overview.

You may also want to learn What is A/B Testing and how it works in Machine Learning.

Note: If you can't access the full article, simply open it in a private tab.

Kamil Jędrzejuk shares an example of one of his early tests and shows how to use good practices and patterns to make them simple and readable.

If you're planning performance testing for your web applications, you may want to start by looking at your data. Vinicius Dallacqua shows how they do it at Spotify.

Moreover, Jonathan Kohl started an interesting series on Load Testing Your Web Infrastructure. You can also read the second and third parts.

A test that depends on the outcome of the previous test is generally an anti-pattern. Güven Karanfil explains how to avoid that.

In relation to that, someone asked on Reddit: Dependent vs independent automated tests?.

Rex Jones II shares a high-level overview and practices that may come in handy when implementing a new test automation framework.

Wondering how you could possibly test CSS? Well, it's not that straightforward, but you can leverage visual testing using Playwright to find unwanted regressions.

Just two weeks ago, I shared with you a simple, high-level guide to running Cypress tests in Safari. Today, I want to highlight a way more detailed guide with examples by Gleb Bahmutov.

Now, that's interesting! In the latest version of Node, you can find node:test — a built-in test framework. David Herron describes it in more detail.

Markus Gärtner gives a great overview of the timeless book Quality Software Management V 1 — Systems Thinking by Gerald M. Weinberg.

Markus also reviewed the second volume of that book — First-Order Measurement.

Have you heard of Healenium — the Selenium tests stabilizer? Here's a 49-minute recording by Anna Chernysheva describing its features.

And if you prefer reading instead of watching, you may want to check out her article.

Just put this bug in the backlog... 😂

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