It looks like you can change the test class to inherit from GWTTestSuite, and use that to add more GWTTestCase subclasses that you define yourself within Eclipse. On Wed, Oct 29, 2008 at 6:39 AM, jbdhl <[EMAIL PROTECTED]> wrote:
> > junitCreator creates one single test class and two launcher-binaries > for that test class. But how are you organizing (and running) unit > tests for *many* classes? I wan't a unit test class for each and every > "real" class in my application but I am not interested in 99 billion > FooBarTest-binaries in my project root dir, I guess? So what then? > > 1) How are you creating *and* organizing test classes for many > classes, not just one? > > 2) How are you organizing the unit tests for the client and server > classes, respectively? The client classes (or at least some of them) > should extend GWTTestCase while the server classes should extend > TestCase. But how do you organize (and run) all of them? > > I'm confused (and a newbie too) > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
