I gave a presentation tonight on the build-test-data grails plugin at the Groovy Users of Minnesota (GUM) meeting that was well received.
Lots of good questions from the people in attendance. Thanks to everyone for showing up.
Here’s a version of it on slideshow:
I also released a new bugfix version of build-test-data earlier today (0.2.2). Mostly fixed bugs, but there’s also a new config setting that lets you disable the plugin in specified environments (suggested by Scott Vlaminck @ refactr.
Does the plugin affect the deployment of the application in any way (such as performance, etc). I think it adds a number of methods to the domain objects, but these are not required for the deployed classes. Are these methods added only for the development build?
Thanks for the excellent plugin.
@Roshan by default, when the plugin is installed, it’s enabled in all environments. This is because there are reasons why you might legitimately want to call build outside of a unit test (ex: if you connect a grails console and want to create some objects to play with, or in your BootStrap script to get some sample objects in the DB).
if you’re not using the build() method in production but you leave the plugin enabled, the only performance impact would be the time it takes for the metaclass to get decorated with the build() method on startup. (i.e. less than a second to startup time). Once the app is running, there would be no impact.
It’s absolutely safe to have the plugin running in production, but the option to turn it off is there for people who want to make sure that their users aren’t calling build() in production code.
Great plugin, it’s saves so much time!
keep up the good work.
[...] Build-Test-Data Presentation [...]
Thanks for this plugin.
[...] with the build-test-data plugin, the documentation on the wiki is thorough, I’ve also given a presentation on build-test-data that explains why it’s better than other existing data generation [...]