Comments on: Grails build-test-data Plugin Released!

By: tednaleid

tednaleid — Tue, 02 Mar 2010 00:06:25 +0000

@madhav test cases normally get rolled back after they’re done so the database isn’t polluted with results. If your tests run successfully, that’s really all that matters :).

If you’re just trying to generate some data to save in your database, you could do it in a “grails console” or even in your BootStrap.groovy file so it’s available when the app is actually running.

By: Madhav

Madhav — Mon, 01 Mar 2010 18:26:09 +0000

I installed plugin and created Functional test case. But data is not persisting in data base . I see test results are success and no error being thowing out.

Can anyone help me whats going on ….

By: tednaleid

tednaleid — Mon, 15 Jun 2009 17:22:37 +0000

Thanks Andrés! I’ll be interested to hear what you think of it.

By: Andrés

Andrés — Mon, 15 Jun 2009 15:31:51 +0000

Ted thank you for your time on developing the plugin and on answering in such a complete way all of the questions people have had.

I have been looking for something like this for quite a lot time now because creating all of the object graph for complex apps is quite boring. Im eager to try your plugin and I hope to come back and give you some feedback about my experience =) Thanks again!

By: Ted Naleid » Grails plugin build-test-data 0.2.1 released

Ted Naleid » Grails plugin build-test-data 0.2.1 released — Mon, 15 Jun 2009 05:37:22 +0000

[...] learn more about the basics of the build-test-data plugin, see this blog post and check out the Basic Usage and Sample Code wiki pages. To install, just run the install-plugin [...]

By: Szymon Polom

Szymon Polom — Tue, 02 Jun 2009 07:55:43 +0000

Regarding the redirection, it happens to me with the newest Firefox 3 on both Vista and Linux.

By: Szymon Polom

Szymon Polom — Tue, 02 Jun 2009 07:54:34 +0000

Thank you for your responses tednaleid.

By: tednaleid

tednaleid — Sun, 31 May 2009 05:34:16 +0000

Thanks for the replies Rob. I think your idea about not setting the dateCreated (as well as dateModified) by default is a good one.

I’ve created an issue on bitbucket to make this change. It’ll be in the next release.

I’ll take a look at the enums too, I thought the code was such that the first enum value was picked for an enum item.

By: Rob Fletcher

Rob Fletcher — Sat, 30 May 2009 20:31:19 +0000

Additionally the joda-time property I’m trying to set is dateCreated which GORM would assign automatically on save so it might be worth getting the plugin to ignore that property even if it’s non-nullable (regardless of whether it’s a joda-time type or a regular java.util.Date).

By: Rob Fletcher

Rob Fletcher — Sat, 30 May 2009 20:11:26 +0000

Even when setting a joda-time property via TestDataConfig or directly in the build call I get the error “Identity property not found, but required in domain class [org.joda.time.DateTime]“.

The enum works so long as I specify a value either in TestDataConfig or the build call.