Issue 57

COMMENT

Welcome to the 57th issue!

This week, we've reached over 2,000 subscribers! 🥳

It's a huge milestone and I'm delighted to see how many of you have enjoyed it so far.

When I started this project just over a year ago, little did I know it would grow so much and turn a hobby into a part-time job.

And the mission of this newsletter has always been to give you access to the best software testing news for free. I'm not planning to change that.

But since some of you asked if there's a way to donate and support my work — you can now buy me a coffee.

Thank you for being a part of it. I try my best to help you learn something new in each issue.

Happy testing! 🙌

NEWS

Benefitting from bugs

Every bug is an opportunity. It is an opportunity to learn and improve the product itself (by fixing the bug), but also an opportunity to enhance our quality engineering practices.

Adam Howard writes about turning bugs into something we can learn from and I feel aligned with this approach.

But what if the developer says "This is not a bug!"? Well, that's another story.

Can I learn software testing on my own?

I'm enjoying this series of answers to common search engine questions about testing by Lee Hawkins. And I found some good piece of advice in this particular one regarding learning software testing on your own.

Team as a Key to "Agile" Quality

Here's a great one from Yevheniia Hlovatska explaining how she and her team shifted to shared responsibility for quality and what benefits it brought.

The Agile Manifesto at 20: What's still relevant—and what's not

It's hard to believe but Agile Manifesto is 20 years old now! This is not only a great occasion to refresh its key values but also evaluate what parts of it are still valid in today's world, as presented by Joris Slob.

What to Consider When Testing an API

If you're testing APIs, Dennis Martinez shares some great tips that can help you get the most out of it.

AUTOMATION

12 Tips for Writing Better Automated Tests

You'll find some universal pieces of advice by Dino Kačavenda on how to do improve your test automation here.

Also, a good addition to that is Przemysław Paczoski's article on the importance of CI/CD and parallelisation.

Anatomy of test automation

I liked this concise breakdown of what effective test automation should be composed of — by Ben Dowen.

Best Websites for Practicing Test Automation

If you're looking for places to practice your test automation skills or try out some new tools in action, here's a great list of resources made specifically for that purpose. Thanks for sharing, David Mello!

Decrease UI tests execution time

One of the best ways to improve the test automation execution time? Containerisation with Docker and Kubernetes that allows easy scaling and parallelism, according to Clément Joye, who just shared this useful guide to setting it all up.

Visualizing Your Automated Testing Strategy

Here's a great article from Luís Soares where he proposes a way to visualise a test automation strategy that can help you spot the untested areas and plan accordingly.

And once you have it, Federico Toledo advises how you can review your software testing strategy.

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

AND...

Hey, I'm a tester... 😅

Issue 57 February 5th 2021