Welcome to the 131st issue!

First of all, apologies for the delayed delivery.

I've just come back from London where we celebrated the 10th birthday of Onfido. It was an absolutely wonderful week and I'm buzzing after seeing 500 of my colleagues in person for the first time.

Now, one of the things I want to bring your attention to in this issue is this Reddit thread: How do you see the future of QA?.

Someone is wondering whether manual testing will be replaced by automation at some point. What I found interesting is the strong arguments against it that people shared in the comments — most of which I agree with.

And now, without further delay, enjoy the news! 🙂

Dawid Dylowicz

Shift-left testing is a great practice for improving quality and confidence in releasing quality features. Louis-Philip Grenier clarifies how it may impact the team and the tester's role.

In relation to that, Paul Grizzaffi explains the Potential Energy of Testing and Automation.

Asmaa Abd El-Monem Seddik shares a lot of great tips on how to perform the requirements and risk analysis that will support testing.

Continuing the great series, Angela Riggs describes metrics that can help you assess your team's workload and capacity.

Make sure to check out the follow-up reads on Measuring Workload To Articulate Pain-Points and Workload Metrics Baby Steps.

Daniel Knott shares important pieces of advice on what to take into consideration when testing mobile apps. He also provides a helpful cheatsheet.

In a similar fashion, Eduardo Fischer dos Santos tells us about A Must For Mobile Testing: Device Farms.

You might have heard or even experienced some of these myths. This is a good reminder from Nataliia Syvynska about why they're not true.

A great complimentary read to that is Maaret Pyhäjärvi's take on Fundamental Disagreements in Testing.

This is a wonderful example of writing a clear and effective test strategy using this simple method. Thanks, Callum Akehurst-Ryan!

Services using Amazon SQS are quite popular these days. Philip Riecks shows examples of creating automated tests for them using Testcontainers in Java.

Thayse Onofrio and Marilene Lourenço wrote a comprehensive guide to test pyramids, describing many variants and advising which one could be used in certain situations.

Looking to start your journey in test automation? Dennis Martinez shares a few important tips on how to avoid feeling overwhelmed.

You might be also better off preparing to answer the One Test Automation Scenario Interview Question that Most Candidates Failed, as Zhimin Zhan explains.

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

Rafaela Azevedo explains what good metrics are and how you can use chaos engineering practices to test your monitoring and alerting systems.

Moreover, you might be interested in Chris Tozzi's explanation of Synthetic Monitoring.

If you're wondering about the pros and cons of the two most popular JavaScript testing frameworks — Cypress and Playwright — then Andrey Enin has something for you.

If you know Puppeteer and you like Python, then Pyppeteer might be the right choice for you. Wanchalerm Popee shows a few examples of using it.

Using JavaScript for testing? Juho Härme wrote a helpful article explaining different ways of using test doubles with Jest.

Also, Kishor Munot tells us about Mocking API Response & Request in Cypress.

Here's an interesting excerpt from Rosemary Wang's book titled Infrastructure as Code, Patterns and Practices that describes using a test pyramid for infrastructure testing.

This is a great, 40-minute talk by Marie Drake and Callum Akehurst-Ryan on the importance of using user stories and acceptance criteria to improve communication and alignment in your team.

Accidents happen... 😅

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.

PS. I'll transfer every donation to Nasz Wybór Foundation which supports Ukrainian refugees in Poland. 🇺🇦 🙏

Dawid Dylowicz