The Dark Side of Being a Test Automation Engineer

Five worst feelings I’ve faced by being a test automation engineer

Sérgio Martins

--

Superman standing alone on top of a building

Fun fact, I started my career as a test automation engineer by accident.

And holy moly, to be honest, I wasn’t too fond of it.

Not like I hated what I did, not that, but I hated that it felt that everyone around me thought that my craft was expendable.

And who loves to feel that we’re going on a path to have an expendable, a.k.a. useless job? — right, no one.

Unfortunately, I’m aware that I’m not the only one that felt like this at a given moment in time, and even worse, this is still a reality in a large and undesired amount of organizations.

5 Feelings You’ve Probably Faced as a Test Automation Engineer

NOTE: Read these with a slight touch of sarcasm and not as the plain and brutal truth that we live in — although it might be for some.

1. Blame Magnet

If you’re familiar with the expression of being a “chick magnet” you certainly understand what we’re talking about here.

As a Test Automation Engineer, part of your job is to implement automated mechanisms to ensure that your product’s features are working as required, which no one cares about because it’s your job. Still, on the other hand, everyone will blame you otherwise.

100% of the time, if there’s an issue found in production, you’re the one to blame. Because you haven’t tested it enough, your automation testing isn’t good enough, or simply because you’re not capable of ensuring the quality of the whole product. And the list goes on.

2. Loneliness

If your job is to cover what everyone else on the team has worked on, there’s no need to be informed beforehand of product decisions that impact the whole product or change the core features’ behavior. You’ll…

--

--

Sérgio Martins

Hey, my name is Sérgio, and I’m a Senior Software Engineer by trade. Here you’ll find short and straight-to-the-point articles related to my craft, and business