I've automated Customer Tests using several different techniques and tools,
from a home-grown framework to HTTPUnit. Here are some lessons I learned:

1) Make sure your customer is getting value out of your automation effort.
Automating to automate isn't necessarily the right thing to do. I think I'd try
not automating first, but still require the team to "run" the tests. If manual
tests reach a point of costing too much, let the customer make the business
decision to have them automated.

2) Who will be looking at the actual tests? If the customer just wants to see
that they run, but doesn't actually write a script, don't try to make the tests
human-readable. Programmer-readable is just fine.

3) Try to have the customer participate in writing the test script. Perhaps you
could write it in English, then turn it into code to automate it. But have the
customer drive what "done" means.

Roy

Automatic acceptance test   Posted by: Trond Andersen,  2002 Nov. 11 05:26 AM RE: Automatic acceptance test   Posted by: Roy Miller,  2002 Nov. 14 09:24 PM