Ranorex performs WPF Instrumentation on System Idle Process

Ranorex Spy, Recorder, and Studio.
uhmdown
Posts: 54
Joined: Mon Apr 03, 2017 12:00 pm

Ranorex performs WPF Instrumentation on System Idle Process

Post by uhmdown » Wed Apr 26, 2017 1:40 pm

My Test Suite produces a warning on the very first Repository item that I try to access.

The SUT is WPF, and the Test Suite actually executes with no problems.
But for some reason, it triggers an ugly warning saying that WPF Instrumentation failed for the System Idle Process (Id 0).

I've spoken to Ranorex support, and although no fix is found as of yet, two workarounds presented themselves:

1. The warning isn't triggered if the Application is already running when the Test Suite execution is started.
2. Suppress the warning so it doesn't taint the report. I achieved this by triggering the Warning in a SmartFolder with a Report Level set to something higher than "Warning".

I went with option 2.
I'm not entirely satisfied with the solution, but I can't chase this issue any longer.


Has anybody else run into this specific variation of the Warning, where WPF Instrumentation is attempted and fails on a non-SUT process (with Id 0), but the rest of the Test Suite runs fine?

uhmdown
Posts: 54
Joined: Mon Apr 03, 2017 12:00 pm

Re: Ranorex performs WPF Instrumentation on System Idle Process

Post by uhmdown » Tue May 02, 2017 8:30 am

I ended up going with a third option.

Created a custom Report Level that is +1 above Warn, and use that for all my warning messages. Then set the global report level to that custom level, trimming away warnings not triggered by myself.

I just hope this won't come back to bite me when there's a legit (but now hidden) warning trying to tell me something important :roll: