Does Ranorex have the ability to support automatic testing of dialogs which are created from Tcl scripts?
If I attempt to inspect a widget on a Tcl created dialog, Ranorex Spy shows the 'checkbox' as a general 'button'. Thus, I can not validate a checked vs un-checked state of the 'checkbox' since it is listed in the XPath as a general 'button.
If Ranorex can not directly validate or use Tcl created dialogs, how are testers using Tcl dialogs in their tests if their AUT makes use of some Tcl created dialogs?
Thanks in advance for any assistance you can provide.
-R
Tcl script
Re: Tcl script
Hi,
Please post a Ranorex snapshot (not screenshot) of the dialog in question. Also, please state your Ranorex version (actual is 6.0.1). It's pretty hard/impossible to suggest something reliable without more details about your app.
Please post a Ranorex snapshot (not screenshot) of the dialog in question. Also, please state your Ranorex version (actual is 6.0.1). It's pretty hard/impossible to suggest something reliable without more details about your app.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Tcl script
My apologies for not posting a snapshot originally. I am posting a snapshot (ref. APLauncherSnapshot.rxsnp) as part of this reply.
My version of Ranorex is 5.4.3.26106 running on Windows XP.
My AUT is also running on the same PC.
I would like to be able validate and use all of the widgets on the dialog shown in the snapshot. However, I am currently focusing on validating and using the 'checkboxes' and I am unable to validate their checked / un-checked state since they are in the path as buttons (not checkboxes). Changing their 'role' type to checkbox makes them un-findable when I attempt to do a 'Highlight Element'.
The 'ConnectOnly' checkbox path is: /form[@title='Launcher']/element/element[@class='TkChild']/element[@instance='0']/button[@class='Button' and @instance='0']
-R
My version of Ranorex is 5.4.3.26106 running on Windows XP.
My AUT is also running on the same PC.
I would like to be able validate and use all of the widgets on the dialog shown in the snapshot. However, I am currently focusing on validating and using the 'checkboxes' and I am unable to validate their checked / un-checked state since they are in the path as buttons (not checkboxes). Changing their 'role' type to checkbox makes them un-findable when I attempt to do a 'Highlight Element'.
The 'ConnectOnly' checkbox path is: /form[@title='Launcher']/element/element[@class='TkChild']/element[@instance='0']/button[@class='Button' and @instance='0']
-R
You do not have the required permissions to view the files attached to this post.
Re: Tcl script
Hi,
Apparently the only way how to validate checked/unchecked state of these "checkboxes" is to validate availability of "Checked" string in AccessibleState: If the AccessibleState of given checkbox does not contain "Checked" then it's most probably unchecked
I would also suggest you to use GDI Capture List (as described here), which could help you with obtaining labels for each button. Although using GDI Capture List could be a bit painful, it's definitely useful in cases Ranorex is not able to obtain some GUI texts due to poor, missing or incorrect implementation of accessibility (typically legacy GUI technologies, which I guess is also a case of TCL?).
Apparently the only way how to validate checked/unchecked state of these "checkboxes" is to validate availability of "Checked" string in AccessibleState: If the AccessibleState of given checkbox does not contain "Checked" then it's most probably unchecked
I would also suggest you to use GDI Capture List (as described here), which could help you with obtaining labels for each button. Although using GDI Capture List could be a bit painful, it's definitely useful in cases Ranorex is not able to obtain some GUI texts due to poor, missing or incorrect implementation of accessibility (typically legacy GUI technologies, which I guess is also a case of TCL?).
You do not have the required permissions to view the files attached to this post.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Tcl script
Thanks for the information! I will give your suggestions a try.
-R
-R