Forum Discussion
Try putting a Delay right before the step that fails. The VM may be running a bit slower than your machine and the test is getting ahead of itself. If that fixes it, we can suggest better ways to handle it than the Delay, but this is a quick way to prove it.
- maumrm6 years agoContributor
Hi Marsha -
Thanks for the idea, I tried a couple different delays and neither one worked. The window is up and shown in the fail screenshot, so it is there, just not recognized during VM testing.
Any other thoughts?
Thanks,
Mike
- Marsha_R6 years ago
Champion Level 3
The window is up and shown in the fail screenshot, so it is there, just not recognized during VM testing."Visible" and "Exists" and "Active" = true don't necessarily all occur at once. In other words, just because you can see it doesn't necessarily mean TC can see it, which is exactly the predicament you are in.
What I would try next is turning Debug on and stepping through the code from a little before the failure happens. See if you can get past the step that way.
- maumrm6 years agoContributor
Thanks Marsha - another piece of the puzzle that may or may not be relevant is that on my desktop this test can be ran w/in TestComplete. The VM is running the test with TestExecute. Is that relevant? I'm not seeing an option to do debugging through TestExecute.
Cheers -
Mike