Welcome to the 59th issue!

The one great thing I discovered this week is the Technology Radar by ThoughtWorks.

It's an overview of the current trends in software development techniques, tools, platforms and languages.

Another cool part is the recommendation level, telling you whether you're good to adapt, trial, assess or hold on with a particular technology.

And since they've been doing it for some time now, you can also search for your favourite technology to check what recommendation they give.

While I wouldn't advise to only rely on a single opinion, I found this radar a great way to either help me reevaluate the technology I already know or spot new trends.

So I'm sure you'll find something interesting there, too.

Happy testing!

Dawid Dylowicz

No matter how hard you try, bugs will always slip through to production. Here's a decent guide by George Lawton about what you can do once they get there.

Also related, Lynda Gaines wrote an interesting comparison of quantifying the cost of fixing vs. preventing bugs.

Just two weeks ago I featured an article on the best websites for practising web automation and now Dennis Martinez lists out even more free places to practice testing of API, mobile, desktop and other areas.

I'm a big fan of releasing frequently while keeping everyone accountable for quality. So I can relate to the good practices that Evgeny Tkachenko listed here.

As an additional read, I can also recommend Quality as a Team Responsibility (Part 2) by Kelly Chin.

Maaret Pyhäjärvi shows that you don't always need to have a written-down test automation strategy when you have principles that you can follow. And, in my opinion, she has some good ones!

There's an interesting story behind the quality process that contributed to Toyota's success and I liked a summary of lessons learned from their approach that Team Merlin brought up here.

This is a solid read if you want to learn about QAOps from different perspectives provided by several experienced software testers.

Another interesting take on this matter is Nate Ballantyne's article What is QAOps?.

Angie Jones talks about the importance of developing and testing a feature within the same sprint and gives good tips on how to achieve it.

Jonathan Thompson did a great job providing many examples of the things you should not do in JavaScript UI testing.

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

This is massive! Federico Toledo and Matias Fornara paired on defining all about functional test automation and they put together this enormous guide that many can learn something valuable from.

Kevin Hicks wonderfully describes how "breaking" your own code can help you deliver quality features. I wish every developer had a mindset like this!

The "Is dead/still alive" debates are never easy to settle unequivocally but maybe they're not supposed to be. Instead, they can be good "hey, wait a second" moments to reflect and adjust some of the current beliefs. And that's how I see this controversially-titled but reasonably-explained opinion on the test automation pyramid by Josh Grant.

I'm very much in line with Alan Page's view on helping developers take over test automation tasks.

If you're looking for test reporting tools, here's a decent list of the free ones working with multiple languages and test automation frameworks that you can try out.

SelectorsHub — the popular free tool for locating elements in the browser — now supports Safari browser, too! Well done, Sanjay Kumar.

When everyone seems to be in love with Cypress test automation framework, it's sobering to see some contrary opinions, too. Zhimin Zhan lists out several limitations that he sees in the tool.

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

Maybe he has a good QA friend... 😁

Thanks for reading!

Enjoying this newsletter? You can support my work and buy me a coffee.

Dawid Dylowicz