Qooxdoo paths
Posted: Tue Nov 18, 2014 4:57 pm
Just a quick warning...I'm really new to Ranorex so this may be trivial.
The GUI I'm attempting to test was built using Qooxdoo controls that are auto-generated based on server content. Unfortunately, when the framework was designed, unique IDs for input fields (i.e. labels) weren't used. See the attached screenshot of the paths generated by Ranorex.
To make things harder, it appears the paths from one build of the GUI SW to the next can change. For example, I'm having a hard time finding McpAdmin (highlighted in screenshot) between the OldGUI and the NewGUI because the path on the base is slightly different.
Is there a way when setting up the Ranorex script that I can make it more dynamic? I'd like to avoid tweaking my Ranorex scripts after every build.
Also, I attempted to capture my Ranorex code per the README at the top of this forum. However, I couldn't figure that out either.
The GUI I'm attempting to test was built using Qooxdoo controls that are auto-generated based on server content. Unfortunately, when the framework was designed, unique IDs for input fields (i.e. labels) weren't used. See the attached screenshot of the paths generated by Ranorex.
To make things harder, it appears the paths from one build of the GUI SW to the next can change. For example, I'm having a hard time finding McpAdmin (highlighted in screenshot) between the OldGUI and the NewGUI because the path on the base is slightly different.
Is there a way when setting up the Ranorex script that I can make it more dynamic? I'd like to avoid tweaking my Ranorex scripts after every build.
Also, I attempted to capture my Ranorex code per the README at the top of this forum. However, I couldn't figure that out either.