Welcome to the 100th issue! 🎉

WOW!

We've made it!

I'm truly astonished at what we've achieved.

I say "we" because without you this project wouldn't make sense.

When I sent the first issue nearly two years ago, I didn't expect it'd get this far.

But look at it now — over 3600 people receive it every week!

I'm unbelievably happy it helps so many of you.

Honestly, thank you so much for your support. 🙏

Happy testing!

PS. One last thing — I promised you the answers to the Ask Me Anything shared last week but it turned out to be too ambitious to deliver in such a short time. My apologies, I'll share the answers with you in the next issue. Stay tuned!

Dawid Dylowicz

What are the good interview questions that check testing knowledge? Here's a great compilation put together by Hannah Son including input from well-known testers.

Additionally, Nick Gilbert gave a bunch of Resume Tips from a Senior QA/Technical Interviewer.

Diogo Nunes put together a few solid heuristics that can help you memorise testing ideas. There are some great references, too.

Similarly, Markus Gärtner shared an interesting way of describing common concepts using a short compilation of Agile "What If"s.

Someone asked on Reddit what to do when developers don't have the testing mindset. You can also find the same question with more answers here.

Maybe one of the potential solutions is getting familiar with the Testing Strategies for Front-End Developers, as Ray suggests.

This is a really solid piece of work from the QA Madness team which put a lot of effort to research, analyse and compile this insightful list of future trends in software development and their impact on testing.

Flavien Huynh describes the process of software quality monitoring using the quality dashboard and quality indicators, including lessons learned after one year of using it on a real project.

What value does test automation bring to software development? Mark Walsh listed out six benefits, including some handy code examples.

In yet another thoughtful article, Dennis Martinez explains why having effective tests is important and what advantages come out of that.

It's a good practice to treat your test automation code like production code. One of the ways of doing that is having solid code reviews in place. Here are some tips on that from Oluwatomi Familoni.

Moreover, you may want to follow Corina Pip's advice on Avoiding The Need to Refactor Your Automation Code.

Curious about Chaos Engineering and wondering what it has to do with testing? Ralfs Bremmers gives a great explanation, mentioning the Netflix approach, providing guidelines and showing a real example.

And if you want to learn more, I can highly recommend the Awesome Chaos Engineering repository maintained by Pavlos Ratis.

Mark Steadman prepared a nice example of setting up and running automated tests on mobile apps using Appium and Axe that can spot accessibility issues.

Postman Flows is the new hot feature of the popular tool that allows to chain requests using the UI instead of code. Beth Marshall did a great job demonstrating its functionality in this step-by-step guide.

This is an interesting opinion by Maaret Pyhäjärvi about the Robot Framework after comparing it to the pytest's ease of use. Turns out there are always better tools!

Alexander Andryashin from Aerokube gives an overview of the new, powerful Lightning Java client for Selenium, including the new features it offers over the other clients.

Serenity BDD has recently released a new version that includes Selenium 4 integration, single browser mode, improved reporting and more. John Ferguson Smart gives more details on the changes.

Matthew Middleton shared a great collection of books, describing how each of them helped him excel at software testing. There's a lot of inspiration here!

If you're new to software testing, you may want to learn from Pramod Dutta's 7-minute video about the fundamental skills for testers.

Mind maps are a great addition to a software tester's toolkit. Here's Prashant Hegde presenting how to use them right in your day-to-day job.

Tester vs Developer... 😂

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