Open simoami opened 10 years ago
Does that happen with all Jasmine tests and only on IE 9?
not all tests that I have. simle tests only. I guess tests that are quickly evaluated. longer ones don't experience this problem. so I thing it's the sequence of events not being respected when they're in the order of milliseconds. Maybe a socket.io thing? but even if it's the case, could we do something to compensate? I wish I was more familiar with how testee handles incoming events. still in the learning curve :)
it happens in IE9 and IE10. IE8 works fine.
I'm facing one issue related to remote VM interaction:
With the "remote" launchpad configuration, I'm able to start any browser on a Windows 7 vm image. The problem is that some tests don't close the remote IE browser. From debugging on the remote client (IE9), I found out that
Testee.end({});
doesn't have any effect with tests that run fast.When I was debugging, I ran
Testee.end({});
command manually from the console after the test has ended, and then the browser closed properly. I have a feeling it's related to socket.io sequencing of events when they're called almost simultaneously, but I might be wrong.Are
end
events conditionally executed on the server side? Can you help debug this issue? It effectively blocks testing on IE since it leaves Testee hanging.All tests are complete.
Testee is stuck