SpringSource发布 Grails 1.2 最终版

jieforest

Testing infrastructure improvements

Non JUnit providers

The test running mechanics have been completely overhauled, opening the door to all kinds of testing possibilities for Grails applications. Previously it was very difficult for non JUnit based tests to be deeply integrated into Grails (e.g grails-easyb). Expect to see testing plugins taking advantage of this new infrastructure.

jieforest

Test phase and type targeting

There is now a more sophisticated mechanism for targeting the exact test you wish to run. Previously, it was only possible to target test phases but it is now also possible to target test types .

You target particular test phases and/or types by using the following syntax:

grails test-app «phase»:«type»
grails test-app unit:spock    // run ‘spock’ test type in ‘unit’ test phase

Either side is optional, and it's absence implies all …

grails test-app unit:    // run all types in ‘unit’ phase
grails test-app :spock    // run ‘spock’ type in all phases

It can be used in conjunction with test targeting…

grails test-app unit: SomeController   // run all test for ‘SomeController’ in the ‘unit’ phase

And is additive…

grails test-app unit: integration:    // run all test types in the ‘unit’ and ‘integration’ phases

Legacy phase targeting syntax is supported for backwards compatibility

grails test-app --unit    // equivalent to grails test-app unit:

jieforest

Clean testing

You can can force a clean before testing by passing -clean to test-app:

grails test-app -clean

jieforest

Echoing System.out and System.err

By default, grails does not show the output from your tests. You can make it do so by passing -echoOut and/or -echoErr to test-app:

grails test-app -echoOut -echoErr

Meod

版主你不能整到一个文件里面：（