Hello and welcome to the 42nd issue!

Thank you all for sending over the great resources on software testing.

I found some very interesting ones and I'll be introducing them to you over the next few weeks.

The first shout-out goes to Maciej Gąsiorowski for creating these two amazing repositories with hundreds of links to handy tools, articles, best practices and much more on the following topics:

1. Quality in Mobile Apps
2. Performance Testing

And if you know more resources like this, you can always let me know here.

Dawid Dylowicz

This is a great read for those who want to understand how sessions work and how they can be tested for potential vulnerabilities. Not a very hard thing, as it turns out, but crucial in checking the security of any web app's authentication. Thanks, Merlin Team!

Whether you're want to get to know what exploratory testing is or you're looking for a simple way to explain the concept to someone, this article by Mariia Hutsuk and Sivamoorthy Bose does a great job in both cases.

"Some tests hold more value than others", says Kevin Lamping. And it's hard not to agree with this reasoning. What I liked the most is the simple formula that he came up with to measure the importance of a test.

Tired of your current job and looking for a change? Dennis Martinez gives some sane reasons why it's good to think it through and give your situation a second look.

On the other side, if you're the employer or the manager, Mihaela Sfat mentions a few things NOT to do when an employee resigns.

If you want to have a better understanding of an SDET role, Aniruddha Biswas did a great job describing its the genesis and characteristics, especially in the Agile context.

I'm really enjoying this series on clean test automation design by Edirin Atumah. In the first part, he created an example with the Page Object pattern. And this part focuses on refactoring that test and optimising the code design. Quality stuff!

I liked these five helpful tips from Axel Hodler on making native iOS test automation faster, easier and more reliable.

This is a cool trick. Giovanni Rago shows how to effectively use cookies to support your test automation efforts in Puppeteer and Playwright frameworks, though it can be applied to other popular JavaScript-based test frameworks, too.

Test automation code can get tricky without proper design techniques. But this guide by Colin Wren shares the benefits of modularising test automation code and shows how to apply it with code examples. I especially liked the atomic approach to building a hierarchy of page objects.

PS. If you can't access the full article, simply open the link in a private tab.

If you're implementing tests in C#, you might be interested in this just-released open-source project by Andy Knight. It's called Boa Constrictor and it's a .NET library that implements the Screenplay Pattern for more clarity in your tests.

Now, this is interesting. Michael Larsen describes Funkify — a Chrome extension tool that helps you understand how people with certain disabilities see your page.

If you're wondering which framework to use for mobile test automation, Itzik Shabtay made a fair comparison of Appium and native mobile frameworks: Espresso for Android and XCUITest for iOS.

That's why we need tests... 😂