On Monday, September 12, 2011 12:33:20 PM UTC+2, Thomas Broyer wrote: > > What do you mean by "GWT's JUnit"? (and actually how do you expect it to > shorten startup or re-compilation time?)
I mean GWT's GWTTestCase extending JUnit that's not redering any UI. Therefore the dev mode re-compilation time could be shortened (must not but could). > > Unit-testing is about software quality. > The most important gains are in the long run, because a set of automated > tests that can be replayed at any time will ensure you don't have > regressions. > For me JUnit is also about TDD. Avoiding regressions is another thing... > With GWT, you should try as hard as possible to use "plain JUnit" (or > TestNG or whatever) tests vs. GWTTestCase, because the former are much > faster; and that's one of the main goals of using MVP (by mocking your view, > you no longer need a GWTTestCase to test your "presenter" logic). > I've hoped for this kind of tips. > This is also where you'll have the most important productivity gains: > writing unit tests for your presenters allows you to develop in short > iterations, without the need to even start up the DevMode. You'd use the > DevMode either early on to design your view, and/or later on to do some > additional manual testing (and actually test your view, rather than your > presenter). > ...and this kind. I guess, I'll give (this time "plain") JUnit another chance. -- 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/-/mosrhPiF4gQJ. 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.
