Ranorex Studio no longer closing browser windows

Ranorex Studio, Spy, Recorder, and Driver.
User avatar
tiffin.filion
Posts: 54
Joined: Thu Oct 29, 2020 12:47 am
Contact:

Ranorex Studio no longer closing browser windows

Post by tiffin.filion » Wed Aug 03, 2022 10:58 pm

I'm wondering if Ranorex Studio 10.2.4 doesn't actually work on Windows 11?

My tests worked fine when I was running 10.1.4 while on Windows 10, but now the Close application action fails. I even created a sample test using the Solution wizard and I still get the same thing.

Code: Select all

Action 'close' failed on element '{WebDocument:Automated GUI Testing Tools}'.
Index was outside the bounds of the array. 
Attachments
Screenshot 2022-08-03 145754.png
screenshot of error
Screenshot 2022-08-03 145754.png (74.62 KiB) Viewed 311 times
-- Tiffin --
Senior QA Analyst

User avatar
tiffin.filion
Posts: 54
Joined: Thu Oct 29, 2020 12:47 am
Contact:

Re: Ranorex Studio no longer closing browser windows

Post by tiffin.filion » Wed Aug 03, 2022 11:38 pm

I should note, if I run a test through BrowserStack and select Windows 11/Chrome, it works fine. It's just my machine where something is broken. :(
-- Tiffin --
Senior QA Analyst

User avatar
tiffin.filion
Posts: 54
Joined: Thu Oct 29, 2020 12:47 am
Contact:

Re: Ranorex Studio no longer closing browser windows

Post by tiffin.filion » Fri Aug 05, 2022 8:25 pm

Did some testing with older versions of ranorex:
10.1.7 & 10.2.2 I have no issues with Close application.
10.2.3 & 10.2.4 I get the index outside of bounds error message.
-- Tiffin --
Senior QA Analyst

User avatar
tiffin.filion
Posts: 54
Joined: Thu Oct 29, 2020 12:47 am
Contact:

Re: Ranorex Studio no longer closing browser windows

Post by tiffin.filion » Fri Aug 12, 2022 6:08 pm

An update, Ranorex Support was able to reproduce so it's an issue with the newer versions of Ranorex running on Windows 11. Just FYI.
-- Tiffin --
Senior QA Analyst

dhale
Posts: 64
Joined: Thu Feb 27, 2014 7:33 pm

Re: Ranorex Studio no longer closing browser windows

Post by dhale » Mon Aug 15, 2022 4:28 pm

Thanks for this post - I came across it while searching to see if anyone else was having similar issue.
I am on Win10 / Edge.
For now, I am going to switch it up a bit and do .Browser.Close() to work around the issue