[
https://jira.codehaus.org/browse/MWEBTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286500#comment-286500
]
Michael Wenig commented on MWEBTEST-4:
--------------------------------------
Hi Siegfried,
sorry for the delay :-)
Currently I do a "clean process-sources webtest:test site site:deploy
webtest:verify-result"
This leads in case of a text failure to a deployed site with the correct
(failing) results. The build in Jenkins is marked as failure (as verify-result
breaks it). It would be better if this build would be marked as unstable so the
user can see this.
So its currently just an optical issue as we cannot distinguish between "test
was not able to run" and "test found some problems" without looking deeply into
the job-console.
Regards Michael
> Plugin should set the correct exit code to mark a build as unstable (like
> JUnit-Test-failures do)
> -------------------------------------------------------------------------------------------------
>
> Key: MWEBTEST-4
> URL: https://jira.codehaus.org/browse/MWEBTEST-4
> Project: Maven 2.x Webtest plugin
> Issue Type: Wish
> Environment: webtest-maven-plugin 0.6.5
> Reporter: Michael Wenig
>
> When a JUnit Test fails the build is marked as unstable (in Hudson). AFAIK
> ist this accomplished by maven and not bvy Hudson by setting some sort of
> exitcode which the report sets.
> It would be great if the webtest-plugin would do that too
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
