Actually, our mocking story improved in 1.5, with the addition of GWTMockUtilities. See that class's javadoc for a sample use with EasyMock.
Note that this allows normal JUnit test cases to create mock instances of GWT widgets. E.g., if you have a controller class and you want a mock of the widget that it drives without having to incur the 20 second GWTTestCase start up penalty, this is for you. If you need to test a widget itself, this won't help you. Oh, and EasyMock rocks. rjrjr On Oct 10, 6:07 am, Ponthiaux Eric <[EMAIL PROTECTED]> wrote: > If you have the time to "mock" your project you're lucky : ). > > Anyway JMock looks better . > > regards . > > Arthur Kalmenson a écrit : > > > This question was already asked a number of times. > > > For server side testing, you can use any mocking framework you want. > > However, for client side testing of GWT specific code, you cannot use > > either mocking frameworks since they utilize reflection. Reflection is > > not supported on the client side for performance reasons. > > > Regards, > > Arthur Kalmenson > > > On Oct 8, 10:02 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > >> Can you use either EASYMOCK or JMOCK for unit testing purposes? Are > >> there any restrictions or problems? > > >> Thanks! > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
