QTP vs Windows Tester Pro - Important

[senthil nathan]

Hi Fred,

I am doing an evaluation on Windows tester pro and our team is already using QTP. QTP is pretty expensive and I would like my team to use Windows Tester Pro, If you have any metrics on the importance of Windows Tester pro and I can present it to the team (Basically Pros and Cons).

Our application is developed on Java Swing and we are struggling to identify controls in the code (windows Tester Pro replay). For that we are using custom control in the code to proceed further and I am taking Java developer help here.

If 60% percent automation can be done by Windows tester pro and will be great for me to proceed with this tool, I don't know how to arrive this percentage now (I am lagging with metrics).

Thanks, Senthil

[Fred G]

Hi Senthil,

Sorry, I don't have any metrics for WindowTester. From my own experience I can give the following pros and cons:

Pro:
-Open source
-No "magic" binding between widgets/controls and test code
-Test code is normal Java code and can therefore be used in a modularized way (reuse, abstraction, etc.)
-In most cases non-standard test features can be added with workarounds (Java hacking)

Cons:
-Small community with few contributions
-At least basic Java knowledge is needed to get the most out of this tool and to structure test cases effectively
-Recording tool needs improvement

Apart from that, your achievable percentage of automation depends on your requirements, the complexity of your application, the use of custom widgets, etc.
So if you have a simple SWT/Swing application which uses standard widgets you have good chance to automate a lot.
If your application is more complex it's going to be harder. And as always the last 20% will take 80% of the time. ;)

Regards,

Fred