To me this kind of article is really illustrating that we are just at the beginning of understanding automated testing. One idea that I think is very interestin

To me this kind of article is really illustrating that we are just at the beginning of understanding automated testing. One idea that I think is very interesting is having the test case abstracted into a meta model and then the different kinds of tests derived from that. Think about the difference in registering an new user using mock objects to mock up from the db to the ui versus the same test scenario using something like htmlUnit. Some things have to change but there is something common to both test scenarios so how can that common part be refactored out? Secondly I think we may see a world where test suites are written by the higher level engineers and the implementation is farmed out to the cheapest bidder. What if there comes a day where we don't even read the actual code any more? Just look at the test report for correctness and that it performs well? In that situation I can imagine the test suite becoming the best design document that software engineering has produced.