[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253657#action_253657
]
Paul Hammant commented on JBEHAVE-394:
--------------------------------------
I'm able to see the problem with the plugin configured yesterday. Its the one
from the aparksinson repo, but it is not the problem for us, JBehave is. Or
its invalid XML output.
Here's one that I guess loaded just fine into the hudson plugin:
<story path="foo.story" title="">
<meta>
<property keyword="@" name="channel" value="aaa"/>
</meta>
<scenario keyword="Scenario:" title="ttt">
<step outcome="failed" keyword="FAILED">Given I am a human with a booked
fff<failure>blort</failure></step>
<step outcome="notPerformed" keyword="NOT PERFORMED">When I cancel the
fff</step>
<step outcome="notPerformed" keyword="NOT PERFORMED">Then I receive an fff is
now canceled</step>
</scenario>
</story>
Here is one that failed:
<story path="bar.story" title="">
<meta>
<property keyword="@" name="channel" value="aaa"/>
</meta>
<filter>+channel aaa -draft</filter>
Note there was no close of <story>, nor was there a <scenario> open or close.
It is like the stream was closed before it was flushed. Incidentally the
second story file (the one that breaks in XML form) has a meta tag that has no
value: @draft. This works fine from the command line of course - and should
cause the story to be ignored for the Hudson run in question.
> 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
