Testing Grails

“Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often.” (Steve McConnell)

Software developers, on the whole, aren't testing nearly as much as they should. But too often this gets translated to, “Write more tests” not, “Write better tests.” We'll talk about the things that should be tested in a typical Grails application, as well as the things that shouldn't be.

In this talk, we'll look at using GroovyTestCases for integration and unit testing. You'll see examples of testing Controllers, TagLibs, and Services. We'll also look at incorporating tools for reporting code coverage. Groovy's strengths in creating mock objects to model behavior are explored as well.

About Scott Davis

Scott Davis is the founder of ThirstyHead.com, a training company that specializes in Groovy and Grails training.

Scott published one of the first public websites implemented in Grails in 2006 and has been actively working with the technology ever since. Author of the book Groovy Recipes: Greasing the Wheels of Java and two ongoing IBM developerWorks article series (Mastering Grails and in 2009, Practically Groovy), Scott writes extensively about how Groovy and Grails are the future of Java development.

More About Scott »