Ranorex Forum

Here a short conclusion about our problem with the debugger. The "behaviour monitioring" of our antivirus has blocked the execution of the generated .exe, when running the test cases. Obviously this has become a problem after the latest TrendMicro update. One option is to deactivate the "behaviour m...

Goods news
After temporarily disabling our antivirus system (trend micro) the debugging was possible without problems.
Our IT will now try to find a way to solve this issue.

Thanks!

Hey, I can understand, that it is hard to tell. Here are the answers to your questions: - it is not possible to debug a clean, new solution, created with 9.0 - older solutions, converted from previous Ranorex versions can not be debugged - downloaded sample here: https://www.ranorex.com/help/latest/...

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 t...

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 ...

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: htt...

Hello, we have the problem that the AUT does not start when debugging mode is enabled. https://i.imgur.com/fKK6Q86.jpg Without debugging mode everything works fine. There is always a black logging screen with no text: https://i.imgur.com/rXWd8eS.jpg When stopping the session, Ranorex hangs. Some mon...

Hello Robert, I did not use the "highlightWithinSurroundingArea" for any other applications under test. I also tried this solution in our "real" application. The problem occurs there, too. Report.Screenshot(ReportLevel.Info, "Screenshot", "", Host.Local.FindSingle("/form[@controlname='FormFramework'...

Thank you for your reply, Alex!

For everyone having the same problem. I just added this script-task to my Bamboo-plan --> Now the .junit.xml file can be parsed

Thanks for your help. In future I will examine the code sample more in detail at first :wink: I have got an additonal question to the Report.Screenshot function. My code looks like this: Report.Screenshot(ReportLevel.Info, "Screenshot", "", Host.Local.FindSingle("/form[@processname='RxDemoApp']"), t...

Hello everyone, we are using the current version of Ranorex (8.3.2). Currently I am trying to set up Ranorex to run via a Bamboo plan. Generally the Ranorex solution can be build successfully. Unfortunately the automatically generated jUnit report cannot be parsed in the according Bamboo-task: simpl...

Hello Robert, thanks for your instruction. Generally it works for me (no adjustments made yet): 2019-01-14 12_37_21-C__Users_q32742_Documents_Maria_06_Workspace_14012019-1103_RanorexBamboo_Ranorex.jpg As you can see the screenshots mostly contain all my used (3) screens. How can I restrict it to onl...

Hello, I had the same problem as b.roddanavar@sap.com. Due to your hint I added the value "all" for the parameter "details": 2019-01-14 11_24_47-RanorexBamboo properties.jpg And I exectued the whole test suite. It works - the report is generated and linked now. There are no more warnings. 2019-01-14...