Welcome to the 191st issue!

Do you want to learn security testing in practice?

This week, I want to highlight the OWASP Juice Shop — a one-stop web app for practising security testing skills.

You can follow the official tutorial that explains all the testing methods step-by-step.

Kudos to Björn Kimminich and Jannik Hollenbach for maintaining this awesome, open-source project.

Happy testing! 🙂

Dawid Dylowicz

Bug priority and severity can sometimes be confusing, so here's a great explanation with examples by Dilara Atesogullari.

Interestingly, Jayateerth Katti explains why "I Don't Report Bug" — or at least not immediately.

Now, that's something new! If you're curious about minimising the environmental impact of testing, Mohit Mair gives some ideas on how to achieve it, including examples of objectives and key results.

Someone's asking for advice on being the first QA in a company. It's a good addition to the other discussion I featured a few weeks ago.

This is a great article by Jeff Nyman, who takes a deep dive into defining testing.

Furthermore, Diogo Nunes wrote down definitions of many Test categories and approaches (Types #2).

Devanshu Bhatt proposes a simplified version of the popular test pyramid enabling a more purposeful and strategic approach to test automation.

Additionally, Manish Saini has some good points on why Tests Should Be Easy to Write and Maintain.

Nikolay Advolodkin advises adding data-* attributes to HTML elements (e.g. data-test-id) to make testing easier, more effective and less flaky. By the way, this approach is also recommended by modern test frameworks, such as Cypress and Playwright.

AWS Lambda functions are gaining popularity thanks to their simplicity and low cost. Felipe Malaquias explains leveraging them for API test automation, an example of which you can see in this repository.

Want to learn how to do test automation on iOS? Asilbek Djamaldinov wrote a great getting-started guide.

And here are the next parts about Unlocking the Power of UI Testing in iOS and Why Mocking Matters in iOS Unit Testing.

If you want to learn how your app performs from the browser perspective, NaveenKumar Namachivayam wrote a handy guide to using k6 for that.

Similarly, Yiğit Taş gives a good overview of general Performance Testing with k6.

This is a detailed, practical guide by Ioan Solderea to security testing using an open-source tool — ZAP.

Playwright has a powerful feature of building custom assertions. Butch Mayhew explains how to leverage that.

Also, Eugene Truuts shows how to Mask Dynamic Elements in Playwright for visual testing.

One of the questions we should ask ourselves when testing mobile apps is how they perform in different network conditions. To simulate that, Rohan Maity shows how to use Flaker on Android.

Someone asked the community what test setup could be used for testing databases and APIs — and people came up with many recommendations.

And in another thread, someone's looking for advice on which tool to use: Selenium? Cypress? Playwright?.

If you're having problems running iOS tests in parallel, Anton Prokuda advises using an open-source tool called Sift.

What is the Black-Box Testing book from 1995 about? And is it still worth reading? This overview by Mike Harris can help you decide.

In this immersive, one-hour recording, Mohsen Mirhoseini invited Zhanibek Marshal to share a story of integrating Maestro as their default testing framework for Android.

Furthermore, Arvind Kumar Bhardwaj wrote an article to help you Discover Mobile Test Automation Framework with Maestro.

Quite a bold statement, isn't it?! If you're curious to find out why Daniel Knott thinks so, check out this 18-minute video.

Bug reproduced... 🤣

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