Ranorex Forum

Hi,

I installed Ranorex 5.4.0.24580 for the purposes of automating a Flex application today. After running the Instrumentation Wizard for Flash/Flex applications successfully, I was still greeted with the Ranorex Technology Limitation popup for Flash/Flex when I tried to use the Ranorex Spy with application.

One thing I noticed is that even with the TraceOutputFileEnable property set to 1 as described in http://www.ranorex.com/support/user-gui ... sting.html, the Debug Flash Player was not creating a log file in any browser I tried - IE, Chrome, Firefox, and Safari.

In this thread, http://www.ranorex.com/forum/windows-8- ... t5671.html, Markus (username: mebner) pointed out that the mm.cfg file should be in the %HOMEDRIVE%%HOMEPATH% directory. This is further supported by Adobe's documentation for configuring the debug Flash player at https://helpx.adobe.com/flash-player/kb ... layer.html.

The article in the Ranorex User Guide linked above says that the Instrumentation Wizard puts it into the %USERPROFILE% directory.

On the machine I was using (with 64-bit Windows 7 Professional), %HOMEDRIVE%%HOMEPATH% and %USERPROFILE% resolve to two different locations:
- %HOMEDRIVE%%HOMEPATH% points to a mapped network drive
- %USERPROFILE% points to %SYSTEMDRIVE%\Users\%USERNAME%

Once I moved the mm.cfg file from %USERPROFILE% to %HOMEDRIVE%%HOMEPATH%, both Ranorex Spy and test execution from Ranorex Studio worked fine and the Flex elements were identified in all browsers.

On a clean VM with Windows 7, both of the paths resolve to %SYSTEMDRIVE%\Users\%USERNAME%.

@Support: While I have managed to get things working in my environment, would it an improvement for the Instrumentation Wizard to place the mm.cfg file in %HOMEDRIVE%%HOMEPATH% as opposed to %USERPROFILE%?

Thanks,
Gabriel

Hello Gabriel,

Great to hear that you could solve your issue.

The suggested functionality is already implemented in the instrumentation process. If %USERPROFILE% differs from %HOMEDRIVE%%HOMEPATH%, the mm.cfg is placed in both locations.

In your case, it could be that there was a permission issue and Ranorex was not able to place the file on the corresponding network drive. The issue could also be caused by a connection problem with the network drive.

Regards,
Johannes