Ranorex Forum

Hello,

I'm trying to detect a 2nd tab in Chrome and Ranorex is having an issue trying to find the DOM when 2 tabs are open. However, it detects the tab if it is the only one open. These tests have worked previously with no issues. I am currently using version 6.2.0. Attached is a screenshot of the two tabs as well as a screen shot of the element. Any help is appreciated!

Hi zoakes,


What Version of Chrome are you using? Because there was a bug with a former version, which should be fixed with the extension 1.0.10.
So you could try to install Ranorex 6.2.1 and the newest version of Chrome.

I hope, this will help.

All good now, thanks!

Hello,

This fixed the problem temporarily but all my test that use a second browser tab are broken again with the same issue described above Are there any other suggestions to fix this issue permanently?

Hi,

Usually, it should work fine to test in different tabs.

Would it be possible for you to upload a Ranorex Snapshot?
This would make it easier to help you with your issue.

Have you already updated our Plugin for Chrome to version 1.0.10 and Ranorex Studio to version 6.2.1?

I have updated to the latest browser plugin and version of Ranorex. Attached is a Ranorex snapshot of the element when there is only 1 browser tab open. It finds the element just fine, however when a second tab is open, the test fails.

Thanks!!

I've experienced the same issue - using the latest version of Ranorex and the latest version of Chrome.

Has there been any resolution?

Thanks!

After not using the tests for about a week I decided to revisit them and they started working again. I am unclear why these tests work one day but not the next. I have not changed any of the configurations or elements since the last tests.

Thanks for your reply zoakes.

By way of example, the module below works fine when the Ranorex.com website is open in Chrome. However, it fails if a second tab is open in Chrome.

Hello Fergal,

The path of the DOM in your case has 2 arguments, one is the URL and the 2nd is the visibility. In your repository you have for the DOM the argument @visible='True'. So it must be visible at the time you run the test in order to be identified.

If you are on another tab, it will not find this DOM.

Regards,

McTurtle

Thanks McTurtle, I deliberately put in the "@visible='True'" to see if the module would work when the tab is visible - it doesn't. Unfortunately the module also fails when that "@visible='True'" is removed from the XPath and two tabs are open in Chrome.

With two tabs open:


With one tab open:

Hi Fergal,

Are you using 64 bit or 32 bit Chrome?
And which spy do you use? 64 or 32 bit?

Could you upload a Ranorex Snapshot?