Chapter 9. Testing your application

 

This chapter covers

  • Testing Griffon applications
  • Using FEST for UI testing
  • The Spock and easyb plugins
  • The CodeNarc, GMetrics, and Cobertura testing and metrics plugins

Let’s pause for a moment and review all you’ve discovered about Griffon so far. First, you’ve learned that all Griffon applications share the same basic structure. You also know that application artifacts are organized by type and responsibility in specific folders on disk. In addition, the MVC pattern is the cornerstone for Griffon’s MVC groups. These, in turn, can be extended by adding other MVC groups within them as members. Finally, you know that you should remember to take threading into account. And you know that all artifacts are glued together via the Groovy language.

You now have models, views, controllers, services, scripts, event handlers, and additional Java/Groovy sources. That’s a lot of stuff! And we’re not even dealing with the extensions provided by Griffon plugins yet. All this leads to the following questions:

  • Where do you start testing?
  • What would be a good strategy for tackling tests?
  • UI testing: go or no go?
  • Is the application solid? Are code paths missing?

9.1. Griffon testing basics

9.2. Not for the faint of heart: UI testing

9.3. Testing with Spock and easyb

9.4. Metrics and code inspection

9.5. Summary