Grails testing setup teardown

These conversations start of in high level generalities and then quickly get to their testing practices in the Grails space since that is where I spend most of my time these days. Admittally the documentation around grails testing is a little light and some of the meta-programming mojo going on behid the covers can be a litte intimidating or confusing for those new to the framework, but falling back on these excuses will enevitably leave you and your app in a bad place.

Plus back in the day pre 1. Call the parent classes setUp method. Call the mockForConstraintsTests method passing in the our domain class. NOTE: This is the class not an instanciatied object. Set the happy path for the domain object. This instance will pass all constraints. Call super. Probably a good thing to do. By extending the GrailsUnitTestCase and calling the super.

Here is what Grails does when we call the mockForConstraintsTests method and pass it our Domain class:. This gives up us cascading validation in our tests. Very cool. If you want to further dig into all of this testing goodness; download the latest version of Grails anything after 1.

But this only works in one way: the target class can access the mixin but the mixin not the target class. For this to work you need to let your mixin implement MixinTargetAware and declare a field named target:. If you rename the test to something without controller everything works fine. In our pre 2. Just use the unescaped value:. I hope this guide and hints help others to avoid the headaches when upgrading your Grails application. This is a very useful article. You are commenting using your WordPress.

You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email.

This site uses Akismet to reduce spam. Learn how your comment data is processed. Skip to content An update in the minor version does not seem like a big step but this is one brought a lot of changes, so here a step by step guide which highlights some pitfalls.

First update the version of Grails in your application properties: app. If you have a lib directory with local jars in your application you need to add this to your repositories as a local directory: grails.

Thanks, have managed to get this working now and with the Remote Control plugin. Although maybe that is what you implied and i read it wrong. I've added my solution to my original question. Solved Thanks to dmahapatro and erdi. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science.

Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked 0. Related Hot Network Questions. Question feed.