Related threads here due to dumb 60 day rule: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/7be51fdddafa219b/ http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/2c182159532c4aa4/
I've found some weirdness when running an Asynch Test using GWTTestCase inside of eclipse. Essentially, one of my classes under test makes a call to Window.alert(as a response to the Asynch response), which was actually getting shown on my system -- but often shown behind the eclipse window so I would see it. As such, a lot of my tests timed out. As an aside, I also wasn't calling timer.schedule with enough time for my server side services to start, so that caused test assertion failures. When I finally commented out the call to Window alert and got the timing right on my timer.schedule(...) and delayFinishTest(...) the test ran fine. Of course, I had to come up with a different way to test my response. In the first thread above, some suggests are made to get around this. My thought is just to find some other modal popup and use that instead of Window.alert. Anyone else with thoughts? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
