you can go to the webtest.properties file and check that
both
haltonerror
and
haltonfailure
are both set to "false"
cheers
Dierk
| -----Original Message-----
| From:
[hidden email] [mailto:
[hidden email]]
| Sent: Montag, 5. Mai 2008 9:48
| To:
[hidden email]
| Subject: [grails-user] Exception handling in WebTest plugin
|
|
| Hi,
|
| the WebTest plugin (tested: 0.3 and 0.4) breaks if an
| exception (i.e. ConnectException) occurs in a test.
| Following tests will not be executed, a HTML report is not generated.
| This is very frustrating if you have embedded webtest in a
| continuous integration/automatic build running on a server
| the developer has no access to.
|
| Example:
| class ExceptionTest extends grails.util.WebTest {
| void suite() {
| testExceptionInWebtest()
| testExceptionInAntGroup()
| }
|
| def testExceptionInWebtest() {
| webtest('Exception In Webtest') {
| throw new Exception()
| }
| }
|
| def testExceptionInAntGroup() {
| webtest('Exception In Ant Group') {
| myStep();
| }
| }
|
| def myStep() {
| ant.group(description:'Here it fails') {
| throw new Exception()
| }
| }
| }
|
| In my opinion webtest should continue on the next test and
| note the exception in the report.
|
| Should I raise an issue for the plugin? Or is it an issue in webtest?
|
|
|
| Best regards
| Marc Pompl
|
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Locked
