Weaponizing Manual Testers
A few months ago, I challenged myself to come up with a snappy title that explained what I did, in a minimal amount of space, and also has my consultancy mentioned in there.
There’s not a lot of real estate, so I came up with: Weaponizer of Manual Testers – archdevops.com
Since that change, I found that a lot of people were attracted to that title. It sounds really cool to weaponize something, and even cooler to weaponize people.
And although it sounds cool, I thought… I wonder if people know what I mean by that?
How Do You Weaponize Manual Testers?
To weaponize people, you give them a skill that can make them dangerous.
It could be anything–teaching them about shooting, fighting, espionage, intelligence.
To weaponize manual testers, I give them a skill that can make them dangerous.
I teach them how to automate. Here’s how:
Learning How to Code
It used to be, you had to be a wizard to write code. Now, languages take care of a bunch of the heavy lifting, and libraries are written to handle specialized instructions.
So that means, the barrier to learning is a lot lower. We don’t have to learn everything about a particular language, just enough for our purposes.
Which, it turns out, isn’t that much.
You might ask, “Why would we need to learn how to code up our own automation when there are so many paid-for tools out there?”
It’s a fair question, and the biggest reason is that it helps you gain independence.
I can’t tell you how many times I’ve seen companies adopt a silver-bullet solution that works great at first, but then with time comes wonky workarounds. Or needed enhancements. Or even bugs.
When that happens, you might be stuck. Will that vendor provide support, or, if what you’re needing doesn’t help their bottom line, will they just let it lapse?
It’s much better to control your automation’s code, so that it can be changed to fit what you need. It also means you can have just enough solution to your problem, instead of trying to take a Swiss Army knife approach.
Level Up the Testing Craft
Testers are extremely powerful. They know how to find bugs.
Not knowing how to automate because of perceived barriers can hamper the testing craft.
What if testers all had a higher level of understanding how to automate? Even if it’s not a ton, if they could automate some tests, or some day-to-day operations, that would help them do a much better job, that would be tremendous.
I help them get there.
That sums up what my consultancy does. That, and helping teams go faster, do better, ship awesomer (is that a word? it is now). www.archdevops.com