Chapter 8. Testing and Continuous Integration
This chapter covers
- Understanding and implementing GWT tests
- Exploring advanced testing techniques, remote and benchmark
- Obtaining code coverage information with GWT tests
- Using continuous integration with GWT projects
A test that reveals a bug has succeeded, not failed.
Boris Beizer
Completing your code and turning out a quality application are not often synonymous nor simultaneous. Beyond the syntax, the compiler, and the resulting bits, a quality application is usually the result of careful design, adequate testing, and proper component integration. These fundamental concepts can be applied to all software projects, but putting them to work with GWT is a bit different than in other environments.
In this chapter, we’re going to follow up on some of the tasks related to building, packaging, and deploying that we addressed in the last chapter, with a focus on testing and automating builds. Along with testing, we’ll also touch on benchmarking in a GWT context. Once we have all the pieces in place, we’ll work through a sample project that utilizes Maven and a continuous integration (CI) server, in order to take full advantage of the complete process. All of these concepts go hand in hand because testing and metrics should ideally be part of an automated build process that’s CI managed.