I wonder if anybody has managed to adapt WinRunner to .NET. Since Mercury is not willing to do that and instead forces you to buy Quick Test Licenses, it might be a good idea.
How could such an extention be accomplished?
Only if you know how mercury programs (what they use...etc) will you be able to do it. Also, you would need to know a "real" language to do so. I dont think they program their program with TSL. [img]images/icons/smile.gif[/img] Other than that, you're probably going to need alot of time not testing to do so...
With all that said, I think the QA Testers here probably wont do it. It takes up alot of time, and they do have a job to do [img]images/icons/smile.gif[/img] Hey, if you want to, i say go for it... You'll make <U>ALOT</U> of friends hehe
Ok, I thought of alternatives also with non-Mercury tools. There is a very little problem:
We would have to re-program what has been established within years.
Unless there is another tool understandig TSL plus has .NET capability plus some other features of WinRunner (e.g. Test Director connection).
I posted at in TestPartner forum because Compuware claims of doing so, but appearently it does not.
In the Mercury support site forums, there are a couple messages from users that say they used a 3rd party .NET add-in for WinRunner. However, the messages say nothing about the source of the add-ins. It could just be people posting fiction in order to get rewards points.
If there is any such 3rd party add-in, I'd love to see it. Even though the .NET applications we need to test are new applications for which there are no pre-existing automated tests, not being able to use WinRunner prevents us from leveraging our existing WinRunner test infrastructure.