[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253794#action_253794
]
Paul Hammant commented on JBEHAVE-394:
--------------------------------------
Folks. Refer to JBEHAVE-420 (nothing to do with Hudson)
I may have fixed the broken XML issue. I am not sure if JBEHAVE-420 relates to
JBEHAVE-394 or not.
> Hudson Plugin to import JBehave reports
> ---------------------------------------
>
> Key: JBEHAVE-394
> URL: http://jira.codehaus.org/browse/JBEHAVE-394
> Project: JBehave
> Issue Type: New Feature
> Components: Hudson Support
> Environment: Hudsdon
> Reporter: Alan Parkinson
> Assignee: Mauro Talevi
> Fix For: 3.2
>
> Attachments: eclipse-jbehave-runner.png, hudson-jbehave-runner.png,
> jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.zip,
> org.jbehave.examples.trader.stories.claims_with_null_calendar.xml, pom.xml,
> TEST--778446379.xml
>
>
> As a developer I want to see a Hudson build test result showing failed
> scenarios so that I can see what broke my build
> As a developer I want scenarios containing pending steps and no failed steps
> to appear in build test result not as a fail or pass so that I can see what
> is missing from a story
> As a Manager I want to see individual scenarios in the build graph so that I
> can monitor progress of stories
> As a Manager I want to see Hudson build trend graph containing failed,
> pending and successful scenarios so that I can monitor the stability of my
> build
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
