Test suite working on 2 Win 7 Pro PC, not working on other 2
Test suite working on 2 Win 7 Pro PC, not working on other 2
I have a Test Suite in Ranorex 7.0.1, that on 1 physical and 1 virtual Win 7 Pro machine works, and on other 2 physical machines, it does not.
Did you encounter this situation? Do you have any idea why this happens?
Please let me know what other details should I give, so you could give me a hand.
I have just attached a snapshot for more details.
Thanks in advance!
Regards,
George
Last edited by gbanica on Tue May 23, 2017 8:41 am, edited 1 time in total.
Re: Test suite working on 2 Win 7 Pro PC, not working on other 2
Hi,
Unfortunately, it's pretty hard (impossible) to tell what's wrong without knowing exact error you getting. It could be due to different Ranorex settings (make sure the settings are stored in Test Suite) or different OS configuration/different VC runtimes, .Net, or 3rd party GUI libs used by your AUT. As mentioned, it's hard to to say what's wrong without more details.
Unfortunately, it's pretty hard (impossible) to tell what's wrong without knowing exact error you getting. It could be due to different Ranorex settings (make sure the settings are stored in Test Suite) or different OS configuration/different VC runtimes, .Net, or 3rd party GUI libs used by your AUT. As mentioned, it's hard to to say what's wrong without more details.
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: Test suite working on 2 Win 7 Pro PC, not working on other 2
Hey guys,
Lay some wisdom on me please.
I am really looking fwd to see your answers / comments.
Have a great day!
George
Lay some wisdom on me please.
I am really looking fwd to see your answers / comments.
Have a great day!

George
Re: Test suite working on 2 Win 7 Pro PC, not working on other 2
As Pavel said, without more information from you, we aren't going to be much help.
You need to include the FULL error message you are getting, at the very least. Any other info would also be helpful.
You need to include the FULL error message you are getting, at the very least. Any other info would also be helpful.
Shortcuts usually aren't...
Re: Test suite working on 2 Win 7 Pro PC, not working on other 2
Hi,
Looking at the snapshot, it seems that Ranorex is not able to recognize DOM element? It suggests there is not installed or enabled Ranorex plugin in Chrome? Eventually, it could be caused by not enabled Global Accessibility option in Chrome. Check for example this post, discussing similar problem.
Looking at the snapshot, it seems that Ranorex is not able to recognize DOM element? It suggests there is not installed or enabled Ranorex plugin in Chrome? Eventually, it could be caused by not enabled Global Accessibility option in Chrome. Check for example this post, discussing similar problem.
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: Test suite working on 2 Win 7 Pro PC, not working on other 2
Hi guys,
Thanks a lot for trying to help me.
I add now further details:
- I converted the open browser action into user code:
Host.Current.OpenBrowser(ipca_login_serveradress, "chrome", "--args --force-renderer-accessibility", true, true, true, false, true);
- I opened the browser like in the Ranorex.rxsettings attached
- I started Ranorex as Windows admin
I hope this sheds more light over the situation I am facing.
Regards,
George
Thanks a lot for trying to help me.
I add now further details:
- I converted the open browser action into user code:
Host.Current.OpenBrowser(ipca_login_serveradress, "chrome", "--args --force-renderer-accessibility", true, true, true, false, true);
- I opened the browser like in the Ranorex.rxsettings attached
- I started Ranorex as Windows admin
I hope this sheds more light over the situation I am facing.
Regards,
George
- Attachments
-
Ranorex.rxsetting.txt
- (19.65 KiB) Downloaded 17 times
Re: Test suite working on 2 Win 7 Pro PC, not working on other 2
Good morning,
we still have troubles getting ranorex working stable.
For example. We try to identify a element with the following xpath
//a[text()='Start Compliance Agent']
When i execute the testcase where the xpath is used five times its working 3/5 five times only .
The error message looks like
Attribute 'InnerText' of element for item 'Ipca_LoginLogout_rxrep.download_StartComplianceAgent' does not match the specified value (Failed to find item 'Ipca_LoginLogout_rxrep.download_StartComplianceAgent'. No element found for path '//a[text()='Start Compliance Agent']' within 30s.).
Screenshot
is there a option to see the xml structure of the side at the time the resolution of the element failed ? Because otherwise its quite difficult to adjust the xpath to get a better result.
Regards Florian
we still have troubles getting ranorex working stable.
For example. We try to identify a element with the following xpath
//a[text()='Start Compliance Agent']
When i execute the testcase where the xpath is used five times its working 3/5 five times only .
The error message looks like
Attribute 'InnerText' of element for item 'Ipca_LoginLogout_rxrep.download_StartComplianceAgent' does not match the specified value (Failed to find item 'Ipca_LoginLogout_rxrep.download_StartComplianceAgent'. No element found for path '//a[text()='Start Compliance Agent']' within 30s.).
Screenshot
is there a option to see the xml structure of the side at the time the resolution of the element failed ? Because otherwise its quite difficult to adjust the xpath to get a better result.
Regards Florian
Re: Test suite working on 2 Win 7 Pro PC, not working on other 2
Hi,
In my opinion, the app simply loads longer than 30s and so the element is not in expected state text()='Start Compliance Agent' during 30secs? And this is why Ranorex fails to find it. What you can do is to increase the search timeout for given element or add Delay before problematic link? Eventually, use WaitFor Exists action.
Also, you can add Log "Snapshot" action right after the failing element (in recording), so you can review the actual state of the app from snapshot saved in realtime. This way you can validate if the element is in expected state (or not).
In my opinion, the app simply loads longer than 30s and so the element is not in expected state text()='Start Compliance Agent' during 30secs? And this is why Ranorex fails to find it. What you can do is to increase the search timeout for given element or add Delay before problematic link? Eventually, use WaitFor Exists action.
Also, you can add Log "Snapshot" action right after the failing element (in recording), so you can review the actual state of the app from snapshot saved in realtime. This way you can validate if the element is in expected state (or not).
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: Test suite working on 2 Win 7 Pro PC, not working on other 2
But in this case its a website. There is nothing left to load. But i´ll check the logs anyways if the error occurs the next time
Re: Test suite working on 2 Win 7 Pro PC, not working on other 2
Hi,
Well, the web-based apps are always a bit tricky to automate, because of possible delays and lags during the page load. As mentioned, try to add Log >> Snapshot action and check if the element is in correct state. My guess is it's not, which may either be a problem with slow page load a there maybe a bug in your AUT?
Well, the web-based apps are always a bit tricky to automate, because of possible delays and lags during the page load. As mentioned, try to add Log >> Snapshot action and check if the element is in correct state. My guess is it's not, which may either be a problem with slow page load a there maybe a bug in your AUT?
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