I'm currently evaluating e-Test, and I have been reading many posts about how e-Tester will require much VBA programming. If you have many scripts written in VBA, what happens when an Object property in the Application being tested changes. In how many places do you have to change the script to get your test script working with the changed app?
That may well be true, but it does not really address the question. You will note that the original post indicated that there was a degree of pre-existing VBA code.
It is true that most cases do not require much or any VBA code. There are however a huge variety of user requirements for eTest and almost every case is unique.
In cases with a large amount of VBA test code, an upgrade of the Application Under Test should only require individual modifications in areas to keep up with changes in object properties etc. It is helpful for instance to define these objects centrally.
As I have indicated though, this is dependant much more upon the quality of the code than the nature of the language used.
"Not every solution was derived to address an obvious problem" - Me (quite recently indeed)