plugin

The latest version of the WebTest plugin for Grails is now available in the central repository.

This is a release to update the plugin to work correctly with 1.2-RC2 and to removed the old run-webtest script in favour of the new test-app -functional integration. If your build server is using run-webtest you will need to change it to test-app -functional

The only known loss of functionality between run-webtest and test-app is the custom test suite behaviour. If you need this functionality do not upgrade (you should also add a Jira to Grails core requesting custom suite functionality from test-app!).

The create-webtest script now re-uses the generation code that comes with Grails and as such supports packages properly but does not generate as much sample code as before (it's basically just a test skeleton). The old method of attempting to generate a basic test for the given domain was not reliable and providing little benefit (imo).

A list of fixed issues is here: http://jira.codehaus.org/browse/GRAILSPLUGINS/fixforversion/16068

Update: latest version is now 1.2.3 containing some installer improvements and test generation bug fixes

The latest version of the Grails WebTest plugin is now available in the main repository. It is a major update to integrate better with the grails test-app hooks and is built using Grails 1.2-M2 (it is backwards compatible with 1.1+). As such there are some manual upgrade steps required (see release notes below). On the plus side, tests will now run as part of test-app and can also access domain classes and plugin code via the groovy step provided by WebTest

There are some trade-offs between using the old run-webtest script and the new test-app support which are outlined below. Hopefully subsequent releases can move all functionality over to the test-app script. Please raise any issues in JIRA against the webtest plugin component.

A new version of the Amazon S3 plugin is now available.

The new release contains changes to help the plugin play nicely in a clustered environment:

• Quartz jobs are now non-volatile and durable to stop them being deleted/recreated when a node is stopped/started
• S3Asset now contains a hostName property (and hence a new column that you will need to add to the DB) which holds the host name of the server that created the row. This allows the plugin job to only try and upload assets where the local file exists on the server that it is running on.