Close button can not be foud after Windows 10 Update

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
mariaspeigl
Posts: 13
Joined: Mon Jan 07, 2019 11:50 am
Location: Germany (Bavaria)

Close button can not be foud after Windows 10 Update

Post by mariaspeigl » Thu May 02, 2019 7:20 am

Hello together,

my computer was updated to the version 1809 of Windows 10.
Now I recognized that my test case to close an application does not work anymore.
The problem is that Ranorex can not find the close-Button.
I updated to Ranorex 9.0.1 and I then I tried to find the element again via Spy:

Image

I can not highlight the close button itself.
Before the update the button was clickable.

Image

My colleague has Windows 7 and the button is clickable by using the same project and test case.

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7470
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Close button can not be foud after Windows 10 Update

Post by odklizec » Thu May 02, 2019 7:28 am

Hi,

Were you able to track the [x] button in previous version of Win 10? Win7 is quite old and UI is completely different, so it does not mean much that your colleague with Win 7 is able to track this button. It's important to know, if it works with previous versions of Windows 10. At next, Ranorex snapshot of the app would be really helpful here. Without, at very least, Ranorex snapshot, there is not much anyone here can do or suggest :)

BTW, have you tried to track [x] button in other apps? Does it work there? I just tried it with outlook and some other apps and it works. So if the problem is isolated to just your AUT, it may be something wrong with the app itself, which makes it incompatible with most recent windows 10?
Pavel Kudrys
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

mariaspeigl
Posts: 13
Joined: Mon Jan 07, 2019 11:50 am
Location: Germany (Bavaria)

Re: Close button can not be foud after Windows 10 Update

Post by mariaspeigl » Thu May 02, 2019 9:01 am

Hello,

thanks your for your response.
Yes I was able to track the button in a previous version von Win10.
This is the reason why I suspect that the update of the operating system could be blamed for it.

The snapshot is attached.

I also tried to track the button of other apps (e.g. IBM Sametime) via Spy, too.
There is the same problem. Spy only recognizes the title bar.
When trying to run the test case the close-Button is not clicked by Ranorex.
Last edited by mariaspeigl on Thu May 02, 2019 1:57 pm, edited 1 time in total.

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7470
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Close button can not be foud after Windows 10 Update

Post by odklizec » Thu May 02, 2019 9:17 am

Well, if the same happens with other apps too, then it's definitely something to check. Tracking definitely works for me, but I'm using English windows and default visual style. From the look of your app, it seems that you are using DE windows and mainly different visual style, which maybe the cause of your problems? I would suggest to switch UI to default Win 10 UI theme, just to see if it helps with tracking, then switch it back. Eventually, contact directly Ranorex support about it. I guess they will initially suggest all the usual steps, like reinstalling Ranorex (complete uninstall and install). And if nothing helps, they may eventually request a remote session with you ;)

Anyway, even though the tracking is not working for you, the UI elements seems to be available in the snapshot? So the below xpath should succesfully find 'Close' button and your old xpath (with childindexes) should work too.
/form[@controlname='FormFramework']/?/?/button[@accessiblename='Schließen']
Pavel Kudrys
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

mariaspeigl
Posts: 13
Joined: Mon Jan 07, 2019 11:50 am
Location: Germany (Bavaria)

Re: Close button can not be foud after Windows 10 Update

Post by mariaspeigl » Thu May 02, 2019 9:58 am

Yes I'm using the DE windows and I'm also using the "default" Win 10 UI theme.
I only have changed the colour of the title bar.
When I set it to "standard" (= no special colour / white), it is white and I can also not find the close button.

I used "childindex=2" to identify the close button of the title bar, due to the fact
that we also run the test cases remotely on a server with an english operating system
(Windows Server 2016 - Version 10.0.14393) and the "name" of the button changes then form "Schließen" to "Close".
I just tried the same test case on the remote server, there the close button gets also clicked by Ranorex.
When tracking it on the server via Spy, Ranorex can identify the close button itself.

The difference is the property "Advanced -> Layout --> Visible".
On the server it is "true", on my computer it is "false".

Thank you for your help.
Maybe I will contact the support directly.
At the moment I have a workaround, because I can select "closing" the AUT via the menu, too.

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7470
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Close button can not be foud after Windows 10 Update

Post by odklizec » Thu May 02, 2019 10:25 am

You can always use both "Schließen" and "Close" in the xpath.
Like this...
/form[@controlname='FormFramework']/?/?/button[@accessiblename='Schließen' or @accessiblename='Close']
or like this...
/form[@controlname='FormFramework']/?/?/button[@accessiblename~'Schließen|Close']
I personally prefer this way over using childindexes, which may change without warning ;)
Pavel Kudrys
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

n1kemax
Posts: 8
Joined: Wed Mar 06, 2019 1:55 pm

Re: Close button can not be foud after Windows 10 Update

Post by n1kemax » Tue Jun 25, 2019 3:02 pm

mariaspeigl wrote:
Thu May 02, 2019 7:20 am
Hello together,

my computer was updated to the version 1809 of Windows 10.
Now I recognized that my test case to close an application does not work anymore.
The problem is that Ranorex can not find the close-Button.
Hi,
Did you solve this problem?

BartoSzu
Posts: 1
Joined: Wed Jan 29, 2020 10:18 am

Re: Close button can not be foud after Windows 10 Update

Post by BartoSzu » Wed Jan 29, 2020 10:21 am

Hi,

Have same issue with finding close button after Win10 update. Ranorex can't find buttons under titlebar.
Have anyone solved somehow this problem?

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7470
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Close button can not be foud after Windows 10 Update

Post by odklizec » Thu Jan 30, 2020 10:56 am

Hi,

I'm afraid, that there are not enough details regarding your issue. Please answer below questions:
Ranorex version? Most recent version is 9.2.1. If you are using something older, please update it.
Is there any error message thrown by Spy or stored in report?
Please share a Ranorex snapshot (NOT screenshot) of the problematic element (or entire app).
Please share the xpath of problematic element, as you are using it in repository.
Pavel Kudrys
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

ahoisl
Certified Professional
Certified Professional
Posts: 192
Joined: Fri Sep 07, 2007 8:16 am

Re: Close button can not be foud after Windows 10 Update

Post by ahoisl » Fri Jan 31, 2020 8:57 am

I think this is the same issue as reported here, you'll also find a workaround:
https://www.ranorex.com/forum/viewtopic ... 809#p55850

We reported this issue to Microsoft already more than a year ago. They already have implemented a fix and said that they will ship it with one of the next updates. Unfortunately, we did not see the fix being shipped, yet...

Regards,
Alex