Merry Christmas! 🎄

I hope you're having a wonderful holiday, free of worries and bugs.

Stay tuned for the next week (that will be next year already!) because I'll share with you a special edition of Software Testing Weekly.

See you in 2021! 😊

PS. This is the last chance to get your business article, service or product featured as a sponsored link at the current price of just $59 per issue. The audience has grown by hundreds over the past months and the price will go up on 1st Jan 2021 to reflect this growth. There are just a few slots left, so book now!

Dawid Dylowicz

The holiday season is a great time to start learning new things and here's a list of the most popular courses from Test Automation University, curated by Angie Jones. Best yet, they're all free!

I don't know much about testing games but I like the way Diego Marin explains the exploratory testing approach to the game mechanics. It shows a new perspective of testing other types of software.

I liked Vineeth Venudasan points on why manual QA processes are inefficient, how shifting-left with test automation can help it and why the full end-to-end UI automation is not the real remedy.

This question on Reddit got my attention, and the replies have some great pieces of advice on how to improve the QA-Dev relationship.

It's hard to test when there are no requirements but this guide by Nicola Lindgren has some good tips on how to navigate testing in such a situation.

Here's an interesting view on the evolving tester's role by Joel Montvelisky.

Jacques Blom explains why using getByRole instead of getByTestId in React application tests is better for writing reliable tests and better code. As Jacques says, it allows testing code in the way that it's used, rather than testing how it's written. I found it very insightful.

In this useful guide, Anton Angelov shows how to use the Fluent Interface design pattern in tests code.

I liked this two-part guide to using a Robot pattern in UI tests by Little Coder Girl.

And if you want to see it in action, make sure to check out the just-published second part about using the pattern in Android tests with Espresso.

I'm a huge fan of treating test code as production code and keeping it clean (i.e readable and reusable). Here's a good example describing testing in Cypress by Klaidas Lekavičius.

Franco Santi wrote a set of decent pieces of advice on the process of choosing the best tool for the testing job.

Vitalii Sotnichenko shows how to integrate CodeceptJS — an open-source solution for end-to-end testing — with popular tools for visual testing.

This is about a software testing book written by Xiaomei Tai that I sadly cannot read, too. But what I enjoyed the most is the very interesting story behind it that James Bach brought up here.

If you want to improve your code architecture skills (which are useful for creating test automation frameworks), then this big list of books on the subject by Thilina Ashen Gamage may come in handy.

And then they ask us to test it... 😅