Inconsistent "Failed to instrument WPF process" problems
Posted: Fri Mar 23, 2018 6:30 pm
I keep running into this problem--our AUT is a desktop application; I'm running Ranorex 8.0.1 on Win10 x64; Ranorex and our app are both running as 32-bit instances; and in my test cases I'm typically launching the application in start-up and closing it in teardown.
I will see this warning and typically get 2-3 failures, in which Ranorex can not find the modal dialog our AUT presents on start-up, while running our test suite of 30+ test cases, and it is not always the same test cases generating it. The log will show the screenshots where the dialog is front and center, but Ranorex can not find it--I assume it's due to this WPF problem each time, although only the first failure displays the warning.
I've gone through several threads about this problem and tried uninstalling/re-installing Ranorex, our AUT, and the .Net Framework. UAC is at its lowest setting. I have the plugin setting at "WPF Preferred". While creating and debugging test cases, I've tried starting Ranorex Studio both as an admin and as a "normal" user for comparison, yet regardless I find quite often while trying to run any particular test case from within Ranorex Studio I will encounter this warning frequently and have to stop and restart the test case, hoping the next time the warning will not resurface.
The inconsistency is incredibly frustrating. Has anyone else encountered this? Any suggestions?
I will see this warning and typically get 2-3 failures, in which Ranorex can not find the modal dialog our AUT presents on start-up, while running our test suite of 30+ test cases, and it is not always the same test cases generating it. The log will show the screenshots where the dialog is front and center, but Ranorex can not find it--I assume it's due to this WPF problem each time, although only the first failure displays the warning.
I've gone through several threads about this problem and tried uninstalling/re-installing Ranorex, our AUT, and the .Net Framework. UAC is at its lowest setting. I have the plugin setting at "WPF Preferred". While creating and debugging test cases, I've tried starting Ranorex Studio both as an admin and as a "normal" user for comparison, yet regardless I find quite often while trying to run any particular test case from within Ranorex Studio I will encounter this warning frequently and have to stop and restart the test case, hoping the next time the warning will not resurface.
The inconsistency is incredibly frustrating. Has anyone else encountered this? Any suggestions?