Ranorex Forum

Mostly this happens if the Ranorex browser extension is not working propperly and is not able to serve the DOM of the page. Reinstrumenting the browser via the Instrumentation Wizzard may fix the problem. If not one common problem is that the extension is not allowed to talk to the "Ranorex Backend"...

I can confirm that the Firefox Extension does not work in Firefox 114 :!: Reinstrumenting (also as admin), reinstalling Firefox, reinstalling RxStudio (10.7 or lower), clearing profiles and browser data does not help. In taskmanager i can see that Firefox 114 does not start the Ranorex.Plugin.Firefo...

Any updates on this topic? The old extension (1.3.1) has been removed from the chrome store already although the new one still does not support ExecuteScript.. It´s a pitty that Ranorex leaves its customers alone with this problem without giving proper advice how and when to migrate to the new exten...

With version 10.5. 1 this issue still persists :( :!: Although according to the release notes this kind of error should be fixed?: Ranorex 10.5.1 Release (December 6, 2022) Bugs Users execute Javascript using ExecuteScript() successfully on an element. Tested with the newest chrome update (108.0.535...

@teltorex

In 10.5.0 this issue still persists when using browser Chrome

This bug seems to be fixed in Ranorex 10.3.0

We are experiencing the exact same issue with version 10.2.4 on Windows 10 . It seems that the close grace period of this action is the problem. With its default value of 0ms the exception gets thrown. With any value greater e.g. 1ms the issue seems to be gone. The issue also effects the actions in ...

Description In our automated CI tests we recently had the problem that when a testcase name contains a colon : the testcase parameters from the commandline will not be passed into the testcase. This seems to be a bug in the design of the CLI syntax. /tcpa|testcaseparam|testcontainerparam:<test cont...

Thanks for your reply. Indeed the fact that the parameter is missing is more of a feature request. BUT the fact that that the generated code gets out of sync with the gui because of this is a bug. Like i said: And when one switches an action from e.g. WaitFor-Exist to WaitFor-AttributeEqual the Time...

This is a RanorexStudio GUI related bug. Description: The WaitFor-Exist and -NotExist actions provide a Timeout parameter in the action table of a recordingmodule which can be bound to a variable. The WaitFor-Attribute* action do not provide this parameter in the action table. rxtimeoutbug.PNG And ...

Hello, I am testing our WPF/WinForms application on windows and now i am trying to validate the content/text property of a multiline text control. I have set the text of the control to the following: Statement1 CR LF Statement2 My validation keeps failing because in the actual value the carriage ret...

Thanks for your reply and suggestion

It´s a pity that there is no such possibility, because identifying the main form of my AUT via processId made my test much more stable in case of left open istances of the same AUT, for example in case of data-driven tests with multiple iterations.

Hello, i am starting my AUT via 'Run application' action and use the returned processId in a xpath to identify the main-form of my AUT. This is very robust if more then one instance/main-form of the AUT exists and works perfectly in production-tests. (Closing AUT later is done via processId too..) W...