Re: [jbehave-user] JBehave Jenkins plugin

[Alex Filatau]

Hi,

Per my understanding, Jenkins plugin is used specifically to get Junit
style results available for your CI system and, for example, fail (or mark
as unstable) a test run results if number of test failures is higher than
configurable threshold.

But I also use HTML Publisher
pluginhttp://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin
 in
my Hudson set up that packages html directory target/jbehave/ and makes it
available on the job page in Hundson as a link to view/reports.html. This
way it's very convenient to look through the failed scenarios and see where
the problem occurred in the context (what's not so convenient with Junit
reports).

Other things that I'd wish to have but not yet figured out how to do are:
- get more useful email report from Hudson showing only stats of failures
and failed scenario/steps
- get additional logging available per scenario as a link in JBehave report
where I could dump some more detailed debugging info not polluting maven
console and Jbehave report
- my Selenium guys need nice solution for screenshot storage location since
they want to arbitrary take screenshots from some steps, dump them in
folder and conveniently look through in gallery view mode

If anyone have some known solutions for that, I'll highly appreciate.

Regards,
Alex Filatau.


On Fri, Jan 24, 2014 at 10:46 AM, Corbin, J.D. jd.cor...@pearson.comwrote:

 Hi,

 I installed the JBehave Jenkins/Hudson plugin (and xUnit) successfully but
 not sure what benefit it provides in regards to viewing reports.  I
 expected that the plugin would allow me to view the JBehave results as part
 of the JUnit reporting tool within Jenkins, but I only ever see Junit
 results and no JBehave.

 I am wondering if there is some configuration element either in Jenkins (I
 did add the post build operation for JBehave 3.x) or in the definition of
 my StoryReportBuilder.

 I would love some help/clarification on using this plugin and what I
 should expect to see in Jenkins.

 Thanks,
 J.D.

Re: [jbehave-user] Result report with css files and images, how to do?

[Alex Filatau]

I might be missing the question, but that's what working for me out of the
box, by deploying jbehave with maven artifact.
You need following dependency:

dependency

 groupIdorg.jbehave.site/groupId

 artifactIdjbehave-site-resources/artifactId

 version${jbehave.site.version}/version

 typezip/type

 /dependency

And then you need for your jbehave-maven-plugin add following execution:


  execution

   idunpack-view-resources/id

   phaseprocess-resources/phase

   goals

   goalunpack-view-resources/goal

   /goals

   /execution


That's it. It results in target/jbehave directory to get images and css etc
in my case.

Or were you asking about customization of all this?


Regards,

Alex Filatau.


On Fri, Oct 4, 2013 at 7:54 AM, Hans Schwäbli
bugs.need.love@gmail.comwrote:

 The test result report of JBehave are HTML files.

 Unfortunately the referenced images and CSS file is not present in the
 target folder.

 I spend quite some time figuring out how to add these resources by some
 Maven configuration, but I could not get it working.

 Is there a small example for dummies showing how to do it? Please with no
 parents, really simple POM file or snippet please.

Re: [jbehave-user] Better JUnit reporting result view

[Alex Filatau]

Sorry for a bit of off topic, but jbehave-junit-runner is indeed great
addition for running JBehave tests and I'd vote for inclusion of it into
standard package if it's proper place to do so. The only thing I'd love to
see there now is ability to go to the step candidate definition by click in
the JUnit report in Eclipse.

Regards,
Alex Filatau.


On Mon, Sep 30, 2013 at 12:33 AM, Hans Schwäbli 
bugs.need.love@gmail.com wrote:

 I wanted to suggest that the JBehave people add such a feature to JBehave.
 It does not make much sense to me to run it as JUnit test and seeing nearly
 nothing in the JUnit view but only in the logs. And a good quality of this
 feature would be more likely.

 Besides this, the Codecentric addon is not as I expect it. If a story has
 given stories then the JUnit view does not show the given stories (which
 must be executed first) but only the actual story.

 As ist seems Codecentric does not use the GivenStories as they are inteded
 by JBehave, because they seem to be using them just to read common data
 (this is how they consulted a cutomer to do).

 But okay, here is the Stacktrace for you. Maybe you can fix and improve it:

 Reports view generated with 0 stories (of which 0 pending) containing 0
 scenarios (of which 0 pending)
 java.lang.RuntimeException:
 org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in
 running stories:
 stories/logout.story:
 org.jbehave.core.embedder.StoryManager$StoryExecutionFailed:
 stories/logout.story
  at
 de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner.run(JUnitReportingRunner.java:81)
  at
 org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
  at
 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
  at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
  at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
  at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
  at
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
 Caused by: org.jbehave.core.embedder.Embedder$RunningStoriesFailed:
 Failures in running stories:
 stories/logout.story:
 org.jbehave.core.embedder.StoryManager$StoryExecutionFailed:
 stories/logout.story
  at
 org.jbehave.core.embedder.Embedder$ThrowingRunningStoriesFailed.handleFailures(Embedder.java:495)
  at org.jbehave.core.embedder.Embedder.handleFailures(Embedder.java:224)
  at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:205)
  at
 de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner.run(JUnitReportingRunner.java:79)
  ... 6 more




 2013/9/27 Robert Hostlowsky robert.hostlow...@codecentric.de

 Hi Hans,

 thanks for your description. So there is a problem when running this
 in the Eclipse junit view, right?
 Can you provide a short snapshot, or just the stacktrace from the console
 view?

 Thx, Robert
 --

 Robert Hostlowsky | Senior Software Developer | Agile Software Factory

 codecentric AG | Landsberger Straße 302 | 80687 München | Deutschland
 www.codecentric.de

 | blog.codecentric.de
 | www.meettheexperts.de
 | www.more4fi.de

 2013/9/27 Hans Schwäbli bugs.need.love@gmail.com:
  As it seems some people from Codecentric have written a custom
 JUnit-Runner
  for JBehave.
 
  It shows what stories and scenarios are run in the Eclipse JUnit view,
 even
  hierarchical.
 
  https://github.com/codecentric/jbehave-junit-runner
 
 https://blog.codecentric.de/files/2012/06/JBehave_JUnit_Results_for_Scenarios_and_Steps.png
 
  But it does not seem to work correctly for jbehave-web-3.6 since a
 exception
  occurs.
 
  Maybe some talented guy can contribute such an feature to JBehave?
 
  I would contribute it myself, but I don't know the JBehave and JUnit
 details
  good enough.

 -
 To unsubscribe from this list, please visit:

 http://xircles.codehaus.org/manage_email