Welcome to the 26th issue of Software Testing Weekly!

It's been precisely half a year since I published the very first issue back in January. Back then I wasn't even sure if this was going to run that long nor whether there would be any interest. Looking back now I know that was one of the best decisions I've made in my QA career.

I want to thank you all for reading, sharing and writing the great news. It hugely contributes to this project and that matters a lot to me.

At this point, I think it's a good time to ask you for your opinion. I would love to hear from you how you find Software Testing Weekly so far and whether you have any suggestions on what you would like to see more of here.

So if you have 30 seconds, please give me your feedback in this super-short survey.

Happy weekend and enjoy the news! 😊

Dawid Dylowicz

This is a big one! Graham Ellis wrote a great three-part series about building a QA team that I found very insightful and learned a lot from.

Here you can read part 1, part 2 and part 3.

I really enjoyed this article by Peter Perlepes that challenges the status quo of Google's testing pyramid and, in a very insightful way, provides an alternate version that we may have not seen before. Neat and clever!

Are you doing demos as part of your testing process? Ash Winter explains why it's a good idea to start doing so by providing a lot of interesting use cases.

In the Agile world, a whole-team approach to quality is a must-do. Alexander Oliveira Dunn provides a sane explanation of why it's beneficial.

Someone shared this story on Reddit and it looks like many people can relate to, guessing by the number of upvotes and comments. This is definitely a problem that should be fixed within companies, which makes Alexander's article above even more relevant.

Thinking that Page Object is the only pattern in test automation? If so, check out this solid review of many other design patterns that can be used there as well. By Anand Bagmar.

A great guide showing how to run Postman API tests on CI from scratch using its CLI tool called Newman. Well done, Ed LeGault!

Venugopal Botla explains in simple words what's the difference between the test and process automation and lists some tools that can be used in each approach.

I was a bit late to find this gem but better late than never! Having done GraphQL API testing this myself, I know it's not a trivial thing to do. That's why I really liked this comprehensive guide prepared by Manoj Kumar. The especially insightful part is about how it can be achieved using various tools!

In this guide, Jakub Skibiński introduces us to an open-source Selenium wrapper — Selenide — by showing code examples and explaining why it might be a great tool for starting with test automation.

Sitespeed.io is an open-source tool I found this week that comes in handy for measuring website's performance. It can be easily integrated with Docker and Grafana for cool monitoring. This guide explains the tool in more detail.

Kristin Jackvony wrote a solid review of this great book on Vladimir Khorikov's recent book on unit testing. Interested in reading it? Good news, it's published for free here, although don't forget to support the author, too!

And moves back to In Progress... 😅