Posts Tagged Grails

Ode to MockFor(March): Part 2 - mockDomain

I know March has long passed. My intentions to do this series during the month of March feel grossly short due to time constrains and a little bit of laziness. In [Part 1][] we started our discussion of the Testing Plugin and how it helps the Grails developer test the constraints on their domain classes. This time around we are going to look at how the Testing Plugin helps you write tests that use all those methods that are injected into your Domain Class at runtime.

Read the rest of this entry »



Grails Environment Checking: Better know a framework

Checking the environment that your Grails application is running.

This is nothing new to Grails 1.1, but I use it quite often and is handy to know.

Lets say you have some code that is dependent on the environment that it is running.

Here is one way to check it:

import org.codehaus.groovy.grails.commons.GrailsApplication
import grails.util.GrailsUtil

//check if production 
if ( GrailsUtil.getEnvironment().equals(GrailsApplication.ENV_PRODUCTION)) ){...}

//check if development
if ( GrailsUtil.getEnvironment().equals(GrailsApplication.ENV_DEVELOPMENT)) ){...}

//check if testing
if ( GrailsUtil.getEnvironment().equals(GrailsApplication.ENV_TEST) ){...}

And here is how you can set the environment in your tests:

import org.codehaus.groovy.grails.commons.GrailsApplication
import grails.util.GrailsUtil

//set envionment to production
System.setProperty(GrailsApplication.ENVIRONMENT, GrailsApplication.ENV_PRODUCTION)

//set envionment to development
System.setProperty(GrailsApplication.ENVIRONMENT, GrailsApplication.ENV_DEVELOPMENT)

//set envionment to test
System.setProperty(GrailsApplication.ENVIRONMENT, GrailsApplication.ENV_TEST)

No Comments

Grails Layouts: Better know a framework

A colleague of mine stated this quote the other day, with a sense of frustration:

Why is there a layout being applied to this view? I’m not assigning a layout to it!

He had recently upgraded a Grails application from 1.0.4 to 1.1, and was now getting a mystery style attached to his template.

So we scratched our heads for a couple minutes and saw that the layout that was being applied had the same name as the controller that was rendering the template.

So we dug through the Grails Docs and saw that Grails 1.1 has applied the convention over configuration paradigm to lay out assignment. Kind of cool if you know about, temporarily frustrating if you don’t.

So here is an example of how it works.

If you have a the following controller in the grails controller directory (grails-app/controllers/)

class BookController {
    def list = {...}

You can then have a layout called grails-app/views/layout/book.gsp

This layout will dynamically be associated to all views the the BookController delegates to.

You can take this a step further and also dynamically assign a layout to a specific action in a view. For this example if we wanted to assign a layout to the list action in the book controller we would just create a template in the following folder:


And the list.gsp layout will be applied to the BookControlelr list action.

My initial reaction to this was one of skepticism:

This is taking convention over configuation a little too far? You are only saving one line of code in your view and it seems to > defiy the principle of least supprise.

If there is one thing I’ve learned it’s that if I have a knee-jerk reaction to something then I usually need to think about it some more.

What I realized is that this now allows us to create more generic and modular views and templates. We can create them with reuse in mind and then skin them for the context that they are being used.

This is cool stuff, you just have to know about it.

No Comments

Ode to MockFor(March): Part 1 - Testing Constraints

Last March, Glen Smith did a wonderfull series on how to write unit tests for your Grails application. This series addressed a major pain point in Grails development at the time: Testing.

A year later and testing your Grails application is much less painfull thanks to the Testing Plugin and its author Peter Ledbrook which has been now been integrated into Grails 1.1

This series is ment to give new users of Grails an overview of how to do Unit Testing using the Testing Plugin (pre Grails 1.1) or just Grails 1.1, and to highlight what the plugin gives you. This will not be an account of what you had to do prior to the Testing Plugin. Just be thankfull you don’t have to travel that road, I know I’m happy to be off it.

First off: Testing Constraints in your Domain Class

Read the rest of this entry »


No Comments