I'm an ASP/VBScript developer. We are lucky enough to have a Quality team that goes through and tests our code before we release anything to our customers/employees. The Quality Team basically goes through a spec line by line and tests each item to make sure it works correctly.
I'm of the opinion that "humans do it better". While I can honestly say that I've never worked with a QA automation application, I kind of wonder if you would spend to much time developing the app and then developing a test for the development process once your done developing (if that makes sense)
.
One of my QA guys happened to walk by as I was writing this and he has actually worked with Mercury products before (he basically agrees with my opinion). It’s much better to have a Functional Specification down on paper. The developer develops from this spec and the QA guy tests the code from the same spec once the code is written. Spending the time to develop a testing script after the code is written just seems to add more time to get the final product out.
I’m kind of curious to see if anyone has had a good experience with it though. In a smaller company where resources are more important then time I could see where this could be useful.