Comment #13 on issue 154 by [email protected]: IronPython compatibility
http://code.google.com/p/robotframework/issues/detail?id=154
Hello all,
meanwhile I solved all my problems reported at comment 9 and manny others.
Most problems are kind of blocking when using MS UI-Automation calls via
IronPython and also beneath in custom written C# wrapper class lib.
The following forum contribution gives me an idea to test the complette
environment on a REAL PC:
http://social.msdn.microsoft.com/forums/en-US/windowsaccessibilityandautomation/thread/7f0bdc7c-be85-4fde-9f8a-cbb3f16ba5f4/
(see the contribution from E RaijarSekhar Reddy at Wednesday, May 05, 2010
8:00 AM)
You will believe or not!
After switching my Test-PC (VMware ESXi Version 4) to my real Office-PC all
my probs are gone!
Weeks of heavy developing workarounds like
1) starting the application for testing seperately in the BAT-file in front
of the start of the test (because Process.Start(...) never returns)
2) working around blocking Invoke-Call with seperate Thread (will not work!
because then it blocks whenn calling the next UI-Automation method).
3) Implementing 'windows opened' event handler for aplication windows,
(witch works badly because the run of the event code may be delayed until
the end of the test (end of RF).
REMEMBER:
When you get (blocking) problems with MS UI Automation and you are on a
Virtual Machine (VM), first leve the VM and switch to a REAL PC. Then you
have a BIG chance to loose all problems!
Now I am sooooo happy!
