Not everything can be tested with unit tests. I write a lot of generator + linker code, so, by necessity, I must use GWTTestCase, as I am testing the compilation process.
If your tests don't involve the gwt generator, then definitely don't incur the overhead of GWTTestCase, but if you are working in the generator layer, or if you want to test a functional gui in the browser, then you should use GWTTestCase. It might be possible with selenium to achieve the in-browser tests, but you will likely need to run the gwt compile anyway, so you might as well just use the testing suite provided. =} On Sunday, September 16, 2012 3:49:38 PM UTC-6, Ed wrote: > > @ tanteanni : > Easiest solution: don't use GWTTestCase... It simple doesn't work well and > if you have it working, it's hard to maintain... > > Try to do everything through unit testing... > Nowedays I can test almost everything through unit tests, and works well. > Google around for "awesome testing with IsWidget", > if I remember correctly, and you find some forum posts of me that might > help you in the correct direction... > > - Ed > -- 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/-/VE4aPJxwRuQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
