Industrial Strength Groovy

You've used Groovy to quickly hack together some short scripts or a simple Grails app. Now you want to treat it more seriously and apply best practices and tools. For Java you'd look at style and coverage checkers, JavaDoc, dependency injection, mocking, testing and build frameworks. For Groovy you have EasyB, Cobertura, CodeNarc, Simian, GroovyDoc, Hudson, Ant, Maven, Gant, Gradle, Spring, Guice, Spock, GMock and more. The talk is packed full of tips and examples for these and other tools.

We'll examine these tools: * EasyB: for writing acceptance tests * Cobertura: for checking code coverage * CodeNarc: for checking code style * Simian: for checking code duplication * GroovyDoc: for writing documentation * Hudson: for CI builds * Maven/Ant/Gant/Gradle: for build files * Spring/Guice: for dependency injection * GroovyMock/Spock: for mocking and testing * OSGi: for writing bundles


About Paul King

Paul King

Paul King leads ASERT, an organization based in Brisbane, Australia which provides software development, training and mentoring services to customers wanting to embrace new technologies, harness best practices and innovate. He has been contributing to open source projects for nearly 20 years and is an active committer on numerous projects including Groovy. Paul speaks at international conferences, publishes in software magazines and journals, and is a co-author of Manning's best-seller: Groovy in Action.

More About Paul »