Ranorex 9 - @Visible='true' being ignored?

[ancleg]

I have an xpath that contains "@visible='true'" in the deepest level of the xpath. However when I spy with it, it is finding some entries that have "Visible=False"

I'd prefer not to post a snapshot but will post a screenshot of what I'm seeing in spy -> https://imgur.com/t3TkwPf

It is finding the first two items correctly, but the third, as shown, has "Visible" -> "False" yet is still showing up.

Edit: When I save a snapshot and open that, it opens in Standalone Spy. There, the "visible=true" does seem to apply, but not within the Spy launched from Studio.

[odklizec]

Hi,

I'm using @Visible a lot in my tests and I'm not experiencing such issue with R9.0? True, I'm not testing SAP-based app, but this should not matter? I think the best you can probably do is to contact directly Ranorex support (via their support form) and request a remote session with them, so they can evaluate the problem in realtime. Without seeing the app under test and actual Ranorex settings, there is very little (if anything) anyone here can do or suggest.

BTW, have you tried to switch back to Ranorex 8.3.2 and evaluate the same xpath?

And one more thing. If standalone spy shows different results than spy started from studio, please check if both spy uses the same settings! Standalone spy and spy started from studio have different set of settings. So try to export the settings from standalone spy and load them in spy started from Studio.

[Support Team]

Hello ancleg,

We introduced a performance feature which could cause this issue in specific situations.
Would you mind trying to disable the setting "Enable JS acceleration for ID9+ without addon" in the plugin settings?
In order to do so please open settings dialog in Ranorex Studio or Ranorex Spy and open the Plugins tab. Navigate to the section "Web" and disable the setting.

Please let me know if this doesn't fix your problem.

Regards,
Bernhard

[ancleg]

Hello ancleg,

We introduced a performance feature which could cause this issue in specific situations.
Would you mind trying to disable the setting "Enable JS acceleration for ID9+ without addon" in the plugin settings?
In order to do so please open settings dialog in Ranorex Studio or Ranorex Spy and open the Plugins tab. Navigate to the section "Web" and disable the setting.

Please let me know if this doesn't fix your problem.

Regards,
Bernhard

That setting (I assume you typoed IE9+, there is no ID9+) is already disabled. Also I am using Chrome, so I'm not sure an IE toggle would affect it.

@odklizec, I have filed a support ticket as well. They have been able to reproduce and are looking into it at that end. I did not jump back to 8.3.2 but I am really trying to avoid moving backwards. We aren't in urgent need of being able to run tests right this moment or else I probably would be panicking

Thanks for your ideas.

[Support Team]

Hello everyone,

After further investigation, we found that our new web performance improvement is causing this issue. Deactivating the setting “Enable JS-based RanoreXPath evaluation” should fix the issue.

Please open the settings dialog in Ranorex Studio (or Ranorex Spy) and navigate to the Plugins tab. Search for the Web section and disable the setting “Enable JS-based RanoreXPath evaluation”.

I hope that helps.

Regards,
Bernhard

[JohnTheTester]

When can we expect a fix of this problem? Or is the JS-based RanoreXPath so unimportant?

Thanks in advance

[odklizec]

Hi,

Have you already tried 9.0.1? It should solve many of found and reported "JS-based..." related 9.0 bugs.

[JohnTheTester]

good morning,

just updated to 9.0.1 and it still does not work. With the plugin enabled ranorex finds 5 elements (but 4 of them are def. not visible).
With the plugin disabled ranorex finds just the one visible.

[odklizec]

Hi,

In this case, I would suggest to contact Ranorex support (via their support form) and if possible, send them a sample HTML/web, which can be used for reproducing this issue. Maybe it's just another edge-case, which was not found and therefore fixed yet?

[JohnTheTester]

First I would like to hear from the support/admin team whether they fixed this at all. The last they wrote was about the work-around.

[ahoisl]

First I would like to hear from the support/admin team whether they fixed this at all. The last they wrote was about the work-around.

As specified in the release notes for 9.0.1, we did improve the visible calculation and definitely fixed problems with the Visible attribute in combination with the JS acceleration.
However, there may still be additional problems that have not been addressed, simply because we did not know them at the time of releasing 9.0.1. We just fixed another case yesterday where the Visible attribute value was wrong and that issue will be fixed with 9.0.2.

To make sure, your use case also works correctly, could you provide us with steps on how to reproduce the problem? Then we could try to reproduce and either verify that our fixes already work or work on a fix for that specific problem. Thank you!

Regards,
Alex
Ranorex Team

[odklizec]

Hi,

Yes, they did. This is from 9.0.1 release notes:

Improved “@visible” attribute calculation to include the current web document viewport when using JS-based search