[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253789#action_253789
]
Alan Parkinson commented on JBEHAVE-394:
----------------------------------------
I'm also seeing corrupted XML files being read by the Hudson plugin before any
processing occurs. When reading a file xUnit will validate the XML file and
then print "[xUnit] [ERROR] - The plugin hasn't been performed correctly:
Conversion error Error to convert - A file not found" in the hudson build
console if the file is not valid XML.
To rule out filters causing problem I will add some unit tests but I don't
think this will be a problem because the XSL is only looking for elements that
decide a test success, fail or skip.
I can now confirm Hudson "Maven2/3" jobs that generate surefire reports are the
cause of missing jbehave reports in the test UI. The other hudson jobs type run
ok) and you can run the examples (without XML corruptions) using maven within a
"freestyle" hudson job and the tests will appear in the UI correctly.
There are related two causes for this problem:
1) Hudson can only process one test report in the UI. Mauro, you might haven
seen two reports in the UI showing the same results and one having the links to
failured test giving a 404.
2) xUnit aggregates test results from other tools to avoid duplicating test
reports. It doesn't do this with the Maven2/3 job as it overrides Hudsons
testing model and adds very Maven specific code. I have been through the xUnit
and Hudson code and I haven't found away of injecting or aggregating the test
results in a "Maven2/3" job to avoid issue 1.
The only way I can see of supporting the "Maven2/3" job within the Hudson
plugin is to write some Hudson Maven specific code which could be complicated.
My suggestion is to document the limitation of job type in the Hudson plugin
and develop a solution for a future release.
> 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
