crazy PowerBuilder 10 and WinRunner, Robot, QARun,
We have migrated from PowerBuilder 8 (ANSI) to PowerBuilder 10 (UNICODE) ... big trouble for Test Automation Tools.
The Test Automation (TA) with PowerBuilder 8 works fine. In the TA-Tool (we use Compuware QARun) all controls (window, button, DW, Edit, ...) could be identified by unique control-name of application (w_1, cb_1, dw_1, em_1, ...). This control-name is set by developer.
Now the Test Automation with PowerBuilder 10 doesn't work like in PB 8.
In the TA-Tool the controls couldn't be identified by unique control-name any more.
Instead of the unique control-name the Label on the control is used for identification (window=title, button=label, DW=label of the control before it, ... ).
If the Label on the control is dynamically changing the unique identification by TA-Tool is nearly not possible.
The reason of this behaviour is PB10 is using character set UNICODE e.g. for asian characters (PB8 use ANSI).
All TA-Tools are listening the WinAPI and window messages. With UNICODE (PB10) the WinApi-function CreateWindowExW is used and with ANSI (PB8) the WinApi-function CreateWindowExA is used.
The Tools identify the control-information in function CreateWindowExA. With PB10 the function CreateWindowExA is not used any more. Therefore the Tools will not find the full control-information like in PB8.
We have a huge TA-script Library of about 1600 scripts for about 50 different applications.
Now the information of control-name is missing for control-identification. All the scripts doesn't work any more.
It seems the only one solution is to adapt all the scripts to the new behaviour of control-identification.
The scripts will not work reliable because the control can dynamically change it's label and therefor it's identifier.
We don't need UNICODE, but unfortunately we have to deal with it. All this because of the $$$ in the eyes of the managers who will sell the product PB10 to the huge asia market ???
The TA-Tool vendors doesn't will adapt PB-support for UNICODE. They mean PowerBuilder will dying off ???
Has anyone else a similar problem with Test Automation for PowerBuilder 10?
Which decision does you take?
Which experience / solution do you have?
Re: crazy PowerBuilder 10 and WinRunner, Robot, QARun,
Locking this topic as it a duplicate.
Happy_Tester, please take due not of the rules of this set of forums, one of which prohibits posting the same question in multiple forums.
(And by the way, what does this have to do with WinRunner?)