13. Testing Your Gwt Application

Testing, and in particular, fully automated testing, is an important part of the GWT development cycle. In this chapter we’ll study ways of doing so in optimal ways, starting with unit tests and ending with integration and acceptance testing.

Why Testing?

The idea of testing software is fairly obvious,1 but the GWT philosophy is based on testing everything automatically, without anybody’s intervention, as an aid to bug prevention and detection at the earliest time.2 The Google Testing Blog (at http://googletesting.blogspot.com/) goes as far as including the motto “Debugging sucks; Testing Rocks” at the top of the page. Another saying is “If it’s not tested, it’s broken”; untested code can (and must be assumed ...

Get Essential GWT: Building for the Web with Google Web Toolkit 2 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.