One thing you should know about unit testing the client code (gwt) of your project is that it's *very very slow*. See more here<http://code.google.com/webtoolkit/doc/latest/DevGuideTesting.html> .
If you're new to unit testing (or only junit?), then I'd recommend writing some tests for a pure java app (perhaps your server code). Not only it's 1-2 seconds fast, but it also gives you valuable knowledge (besides learning, you will suddenly discover object dependencies and possible problems, how to generate objects using factories, how to wire them, how to start test-driven development). Specifically for TDD, here's an example: imagine you write a post-it app, that shares messages between users. Your client code should not allow an empty post-it to be sent to server code, * but* your server code should also handle the case of empty message (either throw an exception, log the message, ignore, etc). Having a test that ensures this correct behavior will save you plenty of time before ever sending any byte through the wire. Hope that made any sense, Alex D. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/XAGgil0FiAgJ. 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.
