Arthur, These rules are just good OO design - when you are depend on interfaces rather than concrete classes. One of the pros of following this principles - you can simplify testing by using mocks instead of real objects. You can read more about why programming to interfaces are so importang.
GWT team offers you MVP (Model View Presenter) pattern - here is a link: http://code.google.com/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html You can find how they hide View's behind interfaces, so you can write tests on presenters. I have a sample project (have not many time for it :( ): https://simpleworklog.svn.sourceforge.net/svnroot/simpleworklog/ It's a maven project, you should have no problems with how to configure it. Please reffer to following test classes as examples of unit-testing: - AdminDashboardPresenterTest.java - LoginPresenterTest.java Hope this helps! -- Kind regards, Ignat Alexeyenko. On Fri, Oct 29, 2010 at 4:14 PM, chrisr <[email protected]>wrote: > Hi Ignat, thank you for the tip. I do remember reading that there is > a way to write gwt junit tests in a way that were much faster than the > way I'm doing it now. I wonder if this is it. > > Is there some documentation for how to write unit tests of this > variety? I searched but didn't come across anything that looked like > what you suggested. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
