On Tue, May 20, 2014 at 1:12 PM, David <david.no...@gmail.com> wrote:
> No I did not try that one. I tried GWT Mockito which looked promising and > I actually managed to test a few widgets until someone added CssResources > and other GWT features and then GWTMockito just exploded with a generic > error that I should try disabling the classloading cache. > > I am using GIN and I never do a GWT.create directly (GIN does that for > you). That helps a lot in testing the higher level classes like Activities. > But it does not really help with widgets. (We have some customisations on > top of the DataGrid and CellTable and it does not look possible to automate > the testing of those. > It isn't clear how much you can do widget tests on the server anyway -- the only way I see it would be useful is widgets that clearly delineate the view from the rest of it, and allow you to test the model/controller. If you are talking about testing your own code, then likewise you don't test the view on the server. -- John A. Tamplin -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM5k6X9yC%2BSbkdPWwQL6aazdKLDhm3cdHwmUB%2BcZf03vAyKrqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
