[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253565#action_253565
]
Mauro Talevi commented on JBEHAVE-394:
--------------------------------------
So, one outstanding thing to verify is how the user accesses the reports. Once
the plugin is configured (e.g. to run the JBehave Core examples), I can see in
the logs:
{log}
[xUnit] [INFO] - Processing JBehave-3.x
[xUnit] [WARNING] - Can't create the path
/Users/mauro/.hudson/jobs/jbehave/workspace/generatedJUnitFiles. Maybe the
directory already exists.
[xUnit] [INFO] - [JBehave-3.x] - 19 test report file(s) were found with the
pattern '**/jbehave/org.jbehave.examples.*.xml' relative to
'/Users/mauro/.hudson/jobs/jbehave/workspace' for the testing framework
'JBehave-3.x'.
[xUnit] [INFO] - Converting
'/Users/mauro/.hudson/jobs/jbehave/workspace/examples/trader/target/jbehave/org.jbehave.examples.trader.stories.after_scenario_outcome.xml'
.
{log}
Other similar lines follow, but I can't see the test reports in the UI Test
Results.
Also, it shows
http://localhost:8080/job/jbehave/3/testReport/junit/org_jbehave_examples_trader_stories_failing_before_scenario/story/We_want_to_show_that_failures_in__BeforeScenario_methods_will_not_prevent_rest_of_scenario_steps_to_run__marked_as_NOT_PERFORMED___Also__the__Before_AfterScenario_failure_messages_should_be_displayed_in_the_output_reports_/
which is blank (showing error 404).
I would just like to clean up these issues.
I agree that publishing it to the Central Plugin repo is a good thing, which
we'll do post release after the dust has settled on the infrastructure.
> 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
