Issue 74

COMMENT

Welcome to the 74th issue!

Do you think bugs only happen to you?

Don't worry, they happen to everyone — all the time!

Only in May, Tesla, Toshiba, Microsoft, the University of California and other big companies suffered from bugs, attacks and data breaches.

Just take a look at Yulia Lomanova's overview of software issues in May.

So bugs — bigger or smaller — are always hiding somewhere there.

And our job is to do the best we can to prevent them. Or at least spot them early.

Happy testing! 😊

NEWS

A Guide to Being a Successful QA Leader

Looking for tips on becoming or improving your skills as a QA Leader? Prashant Hegde shared quite a few of them.

Another solid read that can help you in this matter is Managing self-managed teams by Nilanjan Bhattacharya.

Browser usage from the UK government

If you're curious about browser usage on UK government sites, Matt Hobbs shared A LOT of insightful stats in this thread on Twitter.

My customer found a bug, but I fixed that last

I really enjoyed the story of Farez Rahman dealing with a bug reported by a customer. The first reaction of someone looking at it would be "fix it ASAP", right? Well, not necessarily!

The 9 Risky Shots For Quality Engineering

In this interesting article, Antoine Craske lists out nine challenges that QE has to face to stay relevant in the ever-changing environment of software engineering.

Why I Almost Gave up on Software Testing as a Career

Mirza Sisic reflected on what caused him to think of giving up on the software testing career and then shared some great pieces of advice on how to avoid such a situation.

A related article to that is The 'joy' of finding bugs by Peet Michielsen describing the tester's satisfaction curve.

AUTOMATION

Automation Testing on Microservices

Bishma Nishadi describes the strategy for testing microservices and explains why the test pyramid is not the best approach there.

An introduction to contract testing — Introducing contract testing (Part 2)

This series of articles on contract testing by Bas Dijkstra looks very promising. In case you missed it, you can read the first part here, and stay tuned for many more to come.

How to Decide if You Should Automate a Test Case

Effective automation is not about 100% coverage but about choosing wisely which tests to run, when and how often. Nishi Grover Garg shared a useful checklist that can help you decide.

Quick Guide GitHub Actions on Running Selenium Java Tests

If you're wondering how to set up your Java Selenium tests on Github Actions CI, Anton Angelov got you covered with this straightforward, step-by-step guide.

Speed up Appium iOS Automation

Are your Appium tests running slowly on iOS? Jeeva Tamilselvan has a handful of tips that can help you speed them up!

And speaking of mobile testing, Julia Pottinger shared five quick wins for mobile app testing.

Test doubles

I learned something new from this clear and comprehensive explanation of test doubles by Francisco Iglesias Gómez. Have a read if you're not sure what the difference between dummies, stubs, fakes, spies and mocks is.

BOOKS

The DevOps Handbook (Chapter 10. Enable Fast and Reliable Automated Testing)

This is a detailed and full of insights overview of the 10th chapter of The DevOps Handbook about automated testing. Thanks to Thomas Haver.

AND...

Am I testing the code or... 😂

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.

Issue 74 June 4th 2021