*** Please note that this is the 3rd Tuesday of the month!
"Scriptless" Automation: The Holy Grail?
Test Case maintenance is one of the largest costs that every test group faces.
Business rules change, interfaces change, personnel change, technologies change, what else?
Add to that the prospect of automating those tests. What do you do now? Abandon the manual tests? Can you really do that? As the features grow, can you always run the automation, even before the code has stabilized?
Is management buy-in the barrier to automation? Is it too expensive? You have to buy tools, or if the tools are free, you have to "buy" talent. The automation talent usually doesn't have domain knowledge. Often the domain experts don't have automation knowledge (nor a desire to learn it).
What if you could write tests for manual execution, and as soon as the tests and the code became stable, you could execute them with automation? Without more tests? This is the promise of "scriptless" automation, but who has seen it work? I set out to accomplish this, and achieved good results.
Bio Brent Halvorson
Brent Halvorson is a Software Quality Manager who likes to keep his hands dirty. His experience spans varied domains, including medical devices, digital content management, telco, and risk management. Since every employer has different constraints, he has acquired a good collection of scripting languages, from VBA (and SQABasic) to JScript and Ruby. He has worked with free tools and expensive tools and doesn't have a preference. He is ASQ-certified as a CSQE and CMQ/OE.