WIDGET-ID, test with third-party tools

[Mike Rasch]

Hello,

who has experience with third-party tools for GUI-Test
and can report ?
Wich tools can be used with Progress applications ?
My quick google search found the following:
-WinRunner from Mercury Interactive
-SilkTest from Borland
-RationalRobot from IBM
-TestPartner from Compuware
They all can much more than only GUI test and maybe to big for my requirement.

 

[lloydt]

Hello,

who has experience with third-party tools for GUI-Test
and can report ?
Wich tools can be used with Progress applications ?
My quick google search found the following:
-WinRunner from Mercury Interactive
-SilkTest from Borland
-RationalRobot from IBM
-TestPartner from Compuware
They all can much more than only GUI test and maybe to big for my requirement.

I've heard that Mercury is probably best, but very spendy. We use Testpartner which works ok, but it has one limitation that I do not like, and I'm not so sure the problem rests totally on Compuware. With some components and various activex controls that are used on the gui side of a progress app, Testpartner may not be able to realized the object / widget and extract data/information for use in testing. I'm told that it's due to how Progress instantiates the components and doesn't expose it properly. The same components/activex controls in a VB app work great in Testpartner. vsflexgrid is one such component. In my opinion, and end product appearance/functionality should never be dictated by how testing software interacts. Unfortunately after the purchase of the test software, it usually falls upon the developer to make it work in spite of shortcomings.