Instrumentation seems to not work intermittently
Posted: Thu Jan 03, 2013 10:11 pm
I have a test that uses the Ranorex API to test a Flex website. This test runs automatically from a VM. Every so often, the test will fail to recognize any Flex object. The failure will occur at the same point in the test when the first Flex object is required to be acted on.
My latest attempt to solve this issue was I created a VM with only Ranorex 4.0 installed. So no flash and it has not be instrumented. When I run the test, the VM is restored to the this base state and then I run the instrumentation from the command line with this command:
C:\Program Files (x86)\Ranorex 4.0\Bin\Ranorex.Instrumentation.exe /p:flex /pl /ie /o:false /ft
This way I guarantee that the instrumentation and flash installation is good and not corrupted by a VM snapshot restore operation. My test then runs after this.
This works for the most part. I run this test several times a day automatically. Every 4th or 5th time the test runs it will fail to find any Flex object. The test behaves as if the instrumentation didn't run at all. Each test run has a video recording of the test so I can tell that the instrumentation was ran and I see the output from the command line window that the instrumentation is ran in and I do not see any errors.
Any ideas?
Thanks,
Brandon
My latest attempt to solve this issue was I created a VM with only Ranorex 4.0 installed. So no flash and it has not be instrumented. When I run the test, the VM is restored to the this base state and then I run the instrumentation from the command line with this command:
C:\Program Files (x86)\Ranorex 4.0\Bin\Ranorex.Instrumentation.exe /p:flex /pl /ie /o:false /ft
This way I guarantee that the instrumentation and flash installation is good and not corrupted by a VM snapshot restore operation. My test then runs after this.
This works for the most part. I run this test several times a day automatically. Every 4th or 5th time the test runs it will fail to find any Flex object. The test behaves as if the instrumentation didn't run at all. Each test run has a video recording of the test so I can tell that the instrumentation was ran and I see the output from the command line window that the instrumentation is ran in and I do not see any errors.
Any ideas?
Thanks,
Brandon