Issues with slow object recognition(?) of WinForm objects
Posted: Thu Nov 13, 2014 5:16 pm
I hope the title describes the issue I have well enough. What I mean by ‘slow recognition’ is that on screens constructed using WinForms, the mouse takes a long time to react, get to each action point and then complete the action. On a screen constructed using VB6, the reaction timings and actions are much, much quicker.
I have an ever expanding set of test cases for testing a desktop app. In this app, some of the screens are prebuilt using VB6 and some are created 'On the fly' using WinForms which reference an XML schema (I'm not a developer but this is how it's been described to me). The problem is that Ranorex takes a lot longer to locate the WinForms objects than it does to locate V6 objects
I created a new project and created basic tests for each type of screen and the WinForms screen is still slow.
Basic WinForm Screen test: Basic VB6 Screen test: I can't work out what is causing the issue, apart from the fact they are made with two different technologies. Even using 'set' for the values and tick boxes on the WinForms pages, things don't get any faster I have tried all the methods available in Ranorex for speeding up playback, such as ‘Turbo’, Global settings and adding the mouse move setting in the Program.cs file.
The xPath structures are fundamentally different, but do you think they are they cause of the problem? I have tried changing them in a limited way, but this hasn’t improved things.
Examples of a WinForm xPath:
Example of a VB6 xPath
Not being able to improve this situation will be a major concern, as the majority of the screens we will be testing are made using WinForms and so the tests will get slower and slower to run.
I am currently running a Server 2008r2 VM on a Windows 7 desktop with 3gb of memory. The Ranorex Studio version I am using is 5.2.0
I have an ever expanding set of test cases for testing a desktop app. In this app, some of the screens are prebuilt using VB6 and some are created 'On the fly' using WinForms which reference an XML schema (I'm not a developer but this is how it's been described to me). The problem is that Ranorex takes a lot longer to locate the WinForms objects than it does to locate V6 objects
I created a new project and created basic tests for each type of screen and the WinForms screen is still slow.
Basic WinForm Screen test: Basic VB6 Screen test: I can't work out what is causing the issue, apart from the fact they are made with two different technologies. Even using 'set' for the values and tick boxes on the WinForms pages, things don't get any faster I have tried all the methods available in Ranorex for speeding up playback, such as ‘Turbo’, Global settings and adding the mouse move setting in the Program.cs file.
The xPath structures are fundamentally different, but do you think they are they cause of the problem? I have tried changing them in a limited way, but this hasn’t improved things.
Examples of a WinForm xPath:
/form[@controlname='frmPROPOSER.tst']/?/?/container[@controlname='grpIndividual']/container[@controlname='optAlwaysResidYN']/?/?/radiobutton[@controlname='radYes'] /form[@controlname='frmPROPOSER.tst']/?/?/container[@controlname='grpHave']/checkbox[@controlname='chkProsecutions']Updated from Ranorex Support Team for better readability
Example of a VB6 xPath
/form[@title='Driver']/?/?/element[@controlid='2']/element[@controlid='10']/?/?/radiobutton[@accessiblename='Male'] /form[@title='Driver']/?/?/element[@controlid='26']/?/?/checkbox[@accessiblename~'^Any\ County\ Court\ Judgemen']Updated from Ranorex Support Team for better readability
Not being able to improve this situation will be a major concern, as the majority of the screens we will be testing are made using WinForms and so the tests will get slower and slower to run.
I am currently running a Server 2008r2 VM on a Windows 7 desktop with 3gb of memory. The Ranorex Studio version I am using is 5.2.0