10 Small Testing Tools

In accordance with the doctrine, we have collected our technical requirements for a test automation tool in countless workshops. All requirements are neatly and structurally packed into Excel (because everyone can use it somehow - from the tester to the managing director). Thanks to platforms such as Testtool Review, the tools in question can then be easily found. So, what do we do with the 10 remaining tools?

How about a counting rhyme?

“10 small testing tools can now rejoice, you can’t try one, there were only nine left”

We work with standard technology, program in a standard programming language and use a standard GUI without a lot of bells and whistles. (You can make exciting projects with this too, honestly!) It is incomprehensible why we cannot evaluate a tool ourselves, but have to have it “set up” and “adapted” by the manufacturer and perhaps even pay for it.

“9 No testing tools run overnight.
One crashed too often, so there were only eight left.”

It almost got kicked out of Finale during installation because it just wouldn’t install (again, a boring, freshly installed standard PC). Well, the support was nice and so it worked after all. But it wasn’t stable on any of the 3 workstations used. Even the friendly support was no consolation.

“8 small testing tools, we don’t want to bend, One doesn’t fit into the process, so there were only seven left.”

We are happy to adapt our processes - if there is a reason to do so. A tool can also be a reason for this. Because every manufacturer has probably thought about how the workflow and functions are implemented. And you can assume that the manufacturer has a lot of experience in this area. But it must be possible to argue for it. If it isn’t, then it doesn’t fit.

“7 small testing tools, what do we test first?
Support, sales and offer, now there are six of them.”

When you buy a tool, you always enter into a partnership. Such a commitment is usually long-term and the relationship has to be right. A sales Christmas card (in analog form, perhaps even handwritten) is a nice token of appreciation. But if, after downloading the evaluation version, the sales department calls every day (“Do you have any questions? Can we help?”) and writes emails, it becomes intrusive and even if you have a question, you don’t want to ask it anymore. Even the joy of receiving a Christmas card doesn’t help. You also want a fair “partnership” when it comes to support and the selection of training courses, etc.. Unfortunately, not everyone delivers that…

“We are now playing freely with 6 small testing tools.
We didn’t understand four, there were only two left.”

Test automation tools can be complex and can only be mastered with in-depth training. But they don’t have to be. If experienced software developers and testers are not able to use a tool based on the documentation and their experience, it is questionable whether it can prove itself in daily use. And there is another way, as the two remaining tools prove. Both are so intuitive to use that it is a real pleasure to work with them. Behind closed doors, we even hear that the team members really enjoy implementing tests with them.

“2 small testing tools are now left to choose from, ‘One will, the other won’t’ is clear in any case.”

The two finalists are neck and neck. Now they both have to show what they can do. The final decision will be made at the beginning of 2014. Until then, I’m looking forward to the Christmas cards.