test automation

[jenk]

Jonathan Kohl also has good things to say about Test Automation. A sample:

"Test automation" is a valuable tool we can use in our tester's toolbox to help us do more effective testing. It does not and can not replace a human tester, particularly at the end-user level. It is a sharp tool though, and we can easily cut ourselves with it. Most test automation efforts fail because they don't take software development architecture into account, they don't plan for maintenance, and they tend to be understaffed, and are often staffed by non-programmers. [...] Anyone who claims they can do software test automation without programming is either very naive themselves, or they think you are naive and are trying to sell you something.

Kohl points out the connections between trivializing software testing, thinking that testing itself can be automated (not just some tasks), and poor results. Some of you will nod at Kohl's observation that

When we get it wrong in test automation, [the fallout] is more insidious; it may take a long time to realize a problem is there. By that time, it might be too late. Customers are quietly moving on to competitors, talented testers are frustrated and leaving your company to work for others.

If you're new to test automation, a good primer is Architectures of Test Automation (PDF) by Cem Kaner.

BTW: I know there are 6-7 pro testers / former testers who read my LJ semi-regularly. Also devs & other software folk. Are you comfortable discussing this stuff openly or should I create a filter?