Hi David, Sorry to be late,
gwt-test-utils support all of your stuff (CssRessource, Gin, etc) it' build with java assist wich modify widget bycode on the fly to prevents all call to GWT.create We use it in my project (very big apps in telecom since 2010). About 1000 integration test (full scenario ) and a lot of unit test (Presenter) It's fast, quick to write et easy to run (junit) . It's made by a friend of mine : Gael Lazzari Hope it helps Nicolas 2014-05-20 19:12 GMT+02:00 David <david.no...@gmail.com>: > Hi Nicolas, > > 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. > > And using GWTTestCases is really painful especially since we can't even > proof that we are doing decent code coverage in our tests. > > David > > > > On Tue, May 20, 2014 at 6:19 PM, Nicolas Wetzel <wetz...@gmail.com> wrote: > >> HI ! >> >> did you try gwt-test-utils ? >> it's a very good tool for testing widgets and more without GWTTestCase. >> >> >> >> >> 2014-04-11 21:11 GMT+02:00 David <david.no...@gmail.com>: >> >>> Any plans to improve unit testing abilities so that we might be able to >>> do more unittesting without using GWTTestCase ? >>> >>> I've been trying out gwtmockito as an alternative and it is great, but >>> for unit testing widgets it has many limitations. >>> >>> Sure I am using MVP for the main application logic. But custom widgets >>> are hard to implement and even harder to test the way it currently is. >>> >>> I think with a little help of GWT changes that maybe it could become >>> easier to inject mocks in the right place instead of using class rewriting >>> and other nasty tricks like gwtmockito is doing. >>> >>> For many things having some server side fake for GWT.create would >>> already help a lot (for things like CssResources or Messages it is rather >>> easy to just use some dynamic proxy to fake what you normally generate for >>> the client. Maybe some basic working DOM class would be great as wel, >>> because then most widgets could just be created without much problems. >>> >>> Only the JSNI stuff remains a problem, but maybe if the great ideas of >>> JsInterop and such might make if feasible to even find a solution there ? >>> Or at least putting them in a separate class and using an interface in the >>> widgets to make them mockable for test purposes would be great. >>> >>> One thing that would make GWT a lot easier to mock for testing purpose >>> is if it would embrace an injection framework like GIN or as done in JBoss >>> Errai. You can basically get rid of all the GWT.create invocations and >>> start using @Inject so that we can replace them with either a generated >>> class or a mocked class. >>> >>> David >>> >>> >>> >>> On Fri, Apr 11, 2014 at 8:08 PM, Goktug Gokdogan <gok...@google.com>wrote: >>> >>>> Emma (which is already broken for some cases) is going to go away with >>>> dev mode. We have been talking about js based alternative but I'm not sure >>>> when that will be ready. >>>> >>>> >>>> On Fri, Apr 11, 2014 at 6:44 AM, David <david.no...@gmail.com> wrote: >>>> >>>>> No feedback from the GWT developers ? >>>>> >>>>> >>>>> On Mon, Apr 7, 2014 at 3:09 PM, stuckagain <david.no...@gmail.com>wrote: >>>>> >>>>>> What is the state for supporting Emma with GWTTestCase ? >>>>>> >>>>>> I see that the documentation still refers to a very old version of >>>>>> Emma (and EclEmma). >>>>>> How can we use JaCoCo to do automated testing with code coverage with >>>>>> GWT TestCase ? >>>>>> >>>>>> What will happen when moving to Java 8 ? I guess that the old Emma as >>>>>> referred to in the documentation will have a problem with this (does it >>>>>> even support full Java 7 syntax ?) >>>>>> >>>>>> Will GWTTestCase support remain once DevMode goes away ? or do I >>>>>> understand that wrongly ? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>>>> --- >>>>>> 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. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>>> --- >>>>> 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. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>>> --- >>>> 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. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>> --- >>> 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 >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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/CAO64A8NSwyvzi%2B%2B3gCSkr2akM%3DYUgHZ45ZULkQXNhqTcUc%2BDnQ%40mail.gmail.com<https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAO64A8NSwyvzi%2B%2B3gCSkr2akM%3DYUgHZ45ZULkQXNhqTcUc%2BDnQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CABrJHW1oxZPhUdBaZXWLrZiRLk_h5APmjpWDWDtoS75fsMoFmw%40mail.gmail.com<https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW1oxZPhUdBaZXWLrZiRLk_h5APmjpWDWDtoS75fsMoFmw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAO64A8MUu64CWdLk8spCnX9bcYT690kf-EV6JftRBNmn-3-2dQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
