[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Parkinson updated JBEHAVE-394:
-----------------------------------
Attachment: jbehave-hudson-plugin-0.1.zip
Thanks Ryszard, feedback will be most welcome.
I've gone down the xUnit route and it seems to be working well. Attached is my
latest version that I have been running on my production server for the last 24
hours.
I think I have covered most of the common testing scenarios and it works well
for my projects own stories but there might be the odd edge case I have missed.
> 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
>
>
> 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
