[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245979#action_245979
]
Alan Parkinson commented on JBEHAVE-394:
----------------------------------------
Thanks Seth
I have recreated the problem and it is caused by the XML report from JBehave
being invalid. In this case "failure_followed_by_given_stories.xml" is missing
a closing story tag at the end of the file. I have reported this as JBEHAVE-401
I have made an update to the plugin to fix a bug I have found and moved the
code to github.
https://github.com/aparkinson/jbehave-hudson-plugin/
> Hudson Plugin to import JBehave test reports
> --------------------------------------------
>
> Key: JBEHAVE-394
> URL: http://jira.codehaus.org/browse/JBEHAVE-394
> Project: JBehave
> Issue Type: New Feature
> Environment: Hudsdon
> Reporter: Alan Parkinson
> Priority: Minor
> Attachments: jbehave-hudson-plugin-0.1.zip,
> org.jbehave.examples.trader.stories.claims_with_null_calendar.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
