Welcome to the 133rd issue!

This week, I want to share with you a true gem that I found.

It's the collection of the Awesome Sites To Test On by Butch Mayhew.

So if you're looking for places to practice your testing skills, look no further.

Happy testing! 🙂

Dawid Dylowicz

Javier Lopez explains why it's important to focus on testing the right things the right way and shares handy tips that may help you achieve that.

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

Hales Rymel gives some valuable advice to developers on how to speed up their work delivery by focusing more on testing.

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

Testers often wear many hats. Maik Nogens defines the role of an organisation tester and explains its challenges based on his experience.

Moreover, Ivana Vecchio wrote shares a lot of insights from her experience as a QA in a Data Analytics Team.

Sometimes it's good to look beyond the software testing world and see how other industries approach quality. Here are a lot of interesting insights from Sime Curkovic who analysed the impact of quality on business in the automotive domain.

Joep Schuurkes shares his thoughts on risk-based testing and explains why thinking in terms of impact and likelihood may not be enough.

Daniel Edwards explains why test automation should be part of the development process and gives examples of the unexpected costs that may occur otherwise.

Similarly, Dennis Martinez wrote a great article explaining The Best Time to Start Writing Automated Tests at a Startup.

Here's a short but important list of tips on test automation by Derya Oz that she learned after 10 years in testing.

A good follow-up read to that is Maaret Pyhäjärvi's article about the Four levels of running test automation.

How well do you know the Page Object Model? Blake Norrish wrote a very comprehensive guide with examples.

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

If you work with microservices, you're probably aware of how difficult it can be to test all of the dependencies. Matheus Nogueira shows how test doubles compare to the new approach of trace-based testing, using an open-source tool Tracetest as an example.

Test automation isn't easy. Oleksandr Romanov explains the complexity at each level and assesses which of them are the most complicated.

On the other hand, Olya Kabanova answered the Top 5 Junior Automation Tester’s Questions About Automated Testing.

In this insightful article, Filip Hric compares the top 10 features of Cypress and Playwright using code examples.

Filip also wrote a great article about 8 common mistakes in Cypress (and how to avoid them).

If you're interested in learning about Cypress in more detail, Arya Bharti and Swatantra Srivastava wrote a thorough guide explaining a lot of its features.

Testing in Java? Philip Riecks put together a great, example-based overview of three useful test tools for Spring Boot applications.

There are plenty of API testing tools on the market, so it's no surprise that choosing one might be confusing. You can find a lot of suggestions in this Reddit thread.

Both Playwright and Selenium are one of the most popular tools for web test automation. Wondering which one you should pick up first? Pramod Dutta has some suggestions.

Moreover, here's an interesting conversation on Reddit: Do you see Playwright as a STRONG successor of Selenium?.

Now it's testing time... 😂

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.

PS. I'll transfer every donation to Nasz Wybór Foundation which supports Ukrainian refugees in Poland. 🇺🇦 🙏

Dawid Dylowicz