Unable to Identify Chrome Message Pop-up
Posted: Mon Jun 07, 2021 10:23 pm
Hello folks,
OS: Windows 10 Enterprise 1909
Ranorex Version: 9.3.3+git.bc905490
Chrome: 91.0.4472.77
I don't want to provide a Ranorex snapshot due to the proprietary nature of the application, but I can describe the issue in detail. I'm running into an issue where Ranorex Studio (64-bit)'s repository's "Edit in Spy" as well as the standalone 64-bit Spy, as well as the 32-bit standalone spy can all find a chrome pop-up in the application under the xpath:
/form[@title~'APPNAME' or @title~'APPNAME_TITLE']/container[@accessiblename~'APPNAME']/form[@accessiblename~'URL.*says']
However, when I try to find this pop-up by via a test execution in Ranorex Studio such as a validation that the item exists, it can't find the item when I run it and make sure the chrome window containing the pop-up is in the foreground first. If I leave Ranorex Studio focused and in the foreground, then it can find the pop-up, but not when I have the actual web application in the foreground. This means that if previous tests were already focused on the web application, when it tries to find the pop-up, then the discovery will fail.
An odd difference I can discern is that when I'm in Ranorex Studio and use the "Edit in Spy", it has a warning message:
"One element found for the current selection. The parent repository folder for this item could not be uniquely identified".
However, when I use the standalone Ranorex Spy, it just says "One element found (174ms)".
I've tried many different variations of the xpath to try to get it to find this pop-up when it's visible in the foreground, with no luck. I'm not sure why I keep running into so many differences between different parts of Ranorex.
OS: Windows 10 Enterprise 1909
Ranorex Version: 9.3.3+git.bc905490
Chrome: 91.0.4472.77
I don't want to provide a Ranorex snapshot due to the proprietary nature of the application, but I can describe the issue in detail. I'm running into an issue where Ranorex Studio (64-bit)'s repository's "Edit in Spy" as well as the standalone 64-bit Spy, as well as the 32-bit standalone spy can all find a chrome pop-up in the application under the xpath:
/form[@title~'APPNAME' or @title~'APPNAME_TITLE']/container[@accessiblename~'APPNAME']/form[@accessiblename~'URL.*says']
However, when I try to find this pop-up by via a test execution in Ranorex Studio such as a validation that the item exists, it can't find the item when I run it and make sure the chrome window containing the pop-up is in the foreground first. If I leave Ranorex Studio focused and in the foreground, then it can find the pop-up, but not when I have the actual web application in the foreground. This means that if previous tests were already focused on the web application, when it tries to find the pop-up, then the discovery will fail.
An odd difference I can discern is that when I'm in Ranorex Studio and use the "Edit in Spy", it has a warning message:
"One element found for the current selection. The parent repository folder for this item could not be uniquely identified".
However, when I use the standalone Ranorex Spy, it just says "One element found (174ms)".
I've tried many different variations of the xpath to try to get it to find this pop-up when it's visible in the foreground, with no luck. I'm not sure why I keep running into so many differences between different parts of Ranorex.