So for the first time in many, many years I'm not in a test management position, and I'm writing tests, automating them, etc. We're using a tool called soapUI to automate our web services testing--it's a handy tool, supports Groovy scripting which allows me to go directly to the DB to validate the results of a given method, etc. One feature of soapUI is centralized test scripts; I can create helper scripts to do a bunch of stuff--basically, I write the Groovy code I need to validate something and then I often find I'm moving it into a helper function, refactoring, etc.. My question is, how do you know the right balance between just mashing up the automation (ie, writing a script as an embeded test script) vs. creating the helper function and calling it?
I have to admit, I answered this question a lot as a manager, when my leads would ask me--but now that I'm on the other end, the answer "Just do the right thing" seems a bit, uh, empty. With an 11-year background at MS, my answer was usually "automated everything and do it right - pure OO code". Now that I'm in a faster-paced IT world, that 'balance' seems questionable at times. Especially in an agile environment where we're just moving through these methods left and right - I can barely keep up, coding what I need, and cleaning it up to be readable in the time that I have. Refactoring is almost out of the question.
Anyhow, your feedback would be appreciated. Thanks!!
--
John Overbaugh
blog:
http://thougthsonqa.blogspot.comMSN IM:
john@...Yahoo IM: johnoverbaugh
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
Send Email
