Skip navigation.

Testing tools are like screwdrivers

test tools
It occurred to me while I was at AWTA over the weekend that testing tools are like screwdrivers. There are different types for different problems (Philips and Standard or Performance Testing and Functional Testing), they come in all sorts of different sizes, and they all cost different amounts.

If you think of your average enterprise level automation tool, it’s similar to a mutlihead screwdriver. These tools offer everything under the sun (performance testing, functional testing, test management, defect tracking, data-driven technology, etc…) all you have to do is purchase the tool and start recording! They have a screwdriver bit for every type of testing you might want and several of the bits come in different sizes.

If you look at an open source tool, it’s more like a plain old screwdriver . It only has one head – so it only performs one specific task (like functional testing); and it only comes in one size (so it may only work with a specific technology like Java, .NET, or Internet Explorer). These limitations are often offset by the lower cost (notice I did not say free, someone still has to learn how to use the tool).

Now think about some of the problems you can encounter when using screwdrivers. The most common problem I encounter it that I don’t have the right size screwdriver the job at hand. Sometimes if I use a screwdriver, it’s to small and I can’t exert the force necessary to loosen the screw (common problem with open source tools). Other times it may be too big and I might strip the head of the screw (common problem with enterprise tools). If I own a multiheaded screwdriver, I might lose some of the bits (many companies don’t take the time to learn about all the things their tools can really do for them and thus invest in shelfware).

With this analogy in mind, think about the types of testing you do with your automation tools. Do you need a multiheaded screwdriver or just one right-sized screwdriver? I have been in situations where I’ve needed both. My last project needed a multiheaded screwdriver because I needed to provide and coordinate performance testing and functional testing for multiple platforms using multiple technologies. My current project only needs one or maybe two screwdrivers. We only use one technology an only support one browser.

What kind of screwdriver do you need?

Is it Just screw Drivers?

I liked this article and can make comparisions favourably to a fairly recent (well the 2005 tools issues of Better Software which I only read this week so it is recent to me) with the article by David Gilbert, of http://www.sirius-sqa.com, which talks of the idea of a hammer as one type of tool and how we should have a variety of these and not just hammers but afull tool range to assist us.
James Lyndsay, www.workroom-productions, is also doing a "tool kit" based talk at StarEast in a couple of weeks on the test strategists tool kit, so it seems to becoming a useful and pervaise metatphor fot testing - which fits in nicely with the craftview.
So i am keen to have a range of tools and of different types and costs so that I can be flexable and effective. So I tend to a range of screw drivers for the performance testing, some specialist "allan" keys for the odd specialist piece of work and a workbench to give me the room to work and review the artefacts of testing I have created to see how useful they were (the test managemnt tools).
The hardest part I have with th DIY style tool metaphors is I am useless at DIY, so i may move to a cooking style metaphor and reference knifes myself as I progess the ideas.

Neill McCcarthy
"Agile Testers of the World UNIT !"

From "Staplers" to "ScrewDrivers" to "Open Source Enterprise Tes

TrackBack from testingReflections.com:

Mike Kelly started with Stapler Testing and now he moves onto Screwdrivers . The first was an exercise in “Thinking like a Tester”, t

Re: Testing tools are like screwdrivers

This is an interesting analogy for testing tools, Mike. Continuing on the same theme, my test automation framework that I presented at AWTA is kind of like a power screwdriver with interchangable tips. I provide the "torque" and a holder for "tips", its up to the user of the framework to select the appropriate "tip" (i.e. plug-in testing tool for a particular system under test) and to make sure that it fits into my framework's "holder".

If you don't mind, I may like to refer to this analogy when documenting and describing my framework.

Comment viewing options

Select your preferred way to display the comments and click 'Save settings' to activate your changes.