Welcome to the 163rd issue!

This week, I want to share with you a new, fantastic collection of resources on mobile testing:

How They Automate on Mobile.

It includes articles, discussions, and other resources on mobile testing strategy and automation coming directly from the biggest tech companies.

Kudos to Alexey Alter-Pesotskiy for curating the project.

Happy testing! 🙂

Dawid Dylowicz

We don't always need test cases, but when we do, we should make sure they're well-written. Avinash Kamble gives ten helpful tips on writing great test cases.

Joep Schuurkes recognises the common problem with work planning and suggests a solution based on backlog where features, bugs and technical debt tickets are equally treated.

Furthermore, Nicola Lindgren shares her thoughts on feedback loops, sparked by a frequently asked question during the development lifecycle: Is It Ready For Test?.

How do you make software testing metrics visible? Vincent Ferreira suggests what to measure and how to present it.

Additionally, Itzy Sabo wrote a great overview of the Uptime Guarantees — A Pragmatic Perspective.

Inspired by my comment from the 161st issue, Daniel Delimata shares some interesting thoughts on the future of manual testing.

In relation to that, Ged Smith recognises that "I'm no longer a Tester, I'm a Checker. Or am I?".

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

Lewis Prescott compiled a great, actionable guide helping software testers prepare for a technical interview.

Similarly, Bishnu Prasad Maharana described the Must-Ask Questions for Testing Lead Roles.

And finally, Beth Marshall gives 5 Reasons You Should Consider Creating A Software Testing Portfolio.

Mocking is a popular practice to isolate a subject under test and make testing more focused. But there are some challenges related to this practice, as Irfan Mujagić thoroughly explains using examples.

Furthermore, Sebastian Kuliński advises: Don't Be Fooled by Mocks: Identifying and Avoiding Bad Testing Practices.

Mingyang Li made a great effort to explain the difference between these popular terms which I've often seen used exchangeably.

There are quite a few so-called "test shapes", such as test pyramids, that help describe testing strategy. Carolina Ramirez gives a brief overview of the most popular ones.

And since it's related to the test levels, Wessel Braakman wrote a good Introduction to Contract Testing.

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

Wondering how Spotify load tests its Wrapped feature that summarises a year for millions of users? Well, here's Fred Wang explaining all that!

This is a helpful overview of the most common design patterns for test automation with examples, compiled by Alexander Grossmann.

Speaking of that, Maciej Rojek focused on telling us how to Make Automated Testing Easier with the Page Object Model.

Flakiness is a common problem in test automation. Marcin Wosinek explains where it comes from and how you can improve it in your projects.

Furthermore, Jérémie Fleurant shares insights into How I Managed to Leave My E2E Tests for Months and Find Them All Green.

Finally, you may also want to Use your own undefined method to make your test automation more robust and reliable.

If you don't know where to practice your software testing skills, Andreea Draniceanu describes three powerful places designed specifically for that.

Also, I've recently discovered a new Website to practice Test Automation.

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

This is a very interesting, full-of-opinions thread on Reddit about using Cucumber for test automation.

There's no denying that Cypress and Playwright are the hottest test automation tools right now. So how do they compare? Kailash Pathak explains.

Someone also wonders: How reliable is Playwright?.

With Go recently becoming the 10th most popular programming language, it's worth exploring dedicated test tools. Here's a good overview by Denis Peganov.

If you use Ruby to implement your tests, you might be interested in Roselyne Makena's guide to Capybara — an open-source tool for testing web apps.

If you want to learn more about security testing practices and tools, Rafał Hofman has just released a free book.

Zaeem Ahmed shares his key takeaways from the two-decades-old book titled Effective Software Testing: 50 Specific Ways to Improve Your Testing.

The funniest QA misconceptions... 😂

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