Welcome to the 144th issue!

I want to share with you the true gem I found this week:

Mobile testing strategies from Airbnb, Spotify, Uber and many more.

It's super interesting to see the honest overview from engineers on their approach and struggles.

Happy testing! 🙂

Dawid Dylowicz

Testing mobile apps? Have a read about the test levels test strategy that Raphael Guye, Bryan Reymonenq and Marco Stähli applied to their app.

PS. Thanks for giving me the inspiration for this issue's comment!

No one likes the feeling of bugs being found by your end users. But how can we sort it out? There are lots of ideas and pieces of advice in this Reddit thread.

However, once that happens, here are some great suggestions from Kristin Jackvony on How to Get Your Bug Fixed.

Working in Agile? Mirza Šišić shares a perspective of impacting quality from a product owner's point of view.

Moreover, Vernon Richards wrote a nice summary of the 9 Perspectives Testers Can Use To Understand Their Quality Culture.

Tiger Abrodi brings up some fair points now on why we should and shouldn't test.

In relation to that, Venkat Ramakrishnan explains the Regression Testing Meaning And Purpose.

Vitaly Sharovatov wrote a concise but interesting article on the potential impact of employee turnover on the team and product quality.

Elizabeth Zagroba gives a short description of a software tester's role to someone who's not familiar with it.

What's more, Heather Reid describes how you can Make an Impact in a new job, based on her recent experience.

And finally, James Thomas wrote about the Value Added as a software tester in a new project.

Curious about what processes test automation is made of? Ben Dowen gives a solid, thorough overview.

You may also want to learn about the Automation stories: Stabilization of the parallel test run from Kostiantyn Teltov.

When should you mock the API for testing? And when you shouldn't? Shai Almog shares his point of view.

And whether you mock or not, David Mello's article on Testing Software using Decision Tables may come in handy.

In a series of articles about testing frontend apps, David Obodo explains the different approaches, shows how to set up the first tests and gives advice on how to come up with test scenarios. Here you can find the second and the third parts.

Zhimin Zhan wrote a clear explanation of the web app's basics (HTML, CSS and JavaScript) and how you can test them.

Zhimin also gives examples of Responsive Web Testing with Selenium.

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

If you test APIs with Postman, check out Beth Marshall's six helpful tutorials on testing different flows with it.

Furthermore, Rahul Parwal shows a mindmap of using Postman for Automation in Testing.

Choosing the "best tool" is usually subjective and always depends on the context of a project and the team. It's well visible in this Reddit thread full of various recommendations and explanations.

Wondering what test languages you should use for test automation? This great article by Oleksandr Romanov will give you some hints.

Following up on last week's mention, in the final part of the series Germán Bisogno shows how to use Chrome DevTools protocol to automatically monitor the performance of your web app during testing.

In yet another great overview, Markus Gärtner describes the content and shares the laws from the classic book: An Introduction to General Systems Thinking.

Željko Filipin summarises well every chapter of the Testing Computer Software book.

Small, independent tests are key to reducing flakiness and improving the test execution speed. Nikolay Advolodkin explains how to achieve it with Cypress in this 26-minute tutorial.

In a 7-minute video, Pramod Dutta shares some honest tips for your career that can help you grow faster and potentially benefit from higher pay.

Just keep coding... 😂

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