Brent Barker | 17 Jun 20:51 2014

Story Maping

I am trying to use the Maven plugin for StoryMapping found here:

However, it appears that the <include> tag only looks in src/main/java/

This is the exact maven tag I'm using:

Our stories are located in src/test/resources/stories. I moved a story to the src/main/java and it was able to locate it.

Is there a way to change the path to find where the files are located at a higher level?

Hans Schwäbli | 16 Jun 11:53 2014

Fwd: ContextView still works in 4.0-beta-7?

By the way: You can reproduce it with the same example which I mentioned in another issue:

---------- Forwarded message ----------
From: Hans Schwäbli <>
Date: Mon, Jun 16, 2014 at 8:56 AM
Subject: ContextView still works in 4.0-beta-7?
To: user-b1QraVsTlj/

I changed a project from JBehave 3.9.2 to 4.0-beta-7.
This made the context view disappear. I use the same code for applying the context view like I see in the JBehave examples today (org.jbehave.examples.core.CoreStories).
Does the ContextView still work in JBehave 4.0-beta-7?

Hans Schwäbli | 16 Jun 08:56 2014

ContextView still works in 4.0-beta-7?

I changed a project from JBehave 3.9.2 to 4.0-beta-7.
This made the context view disappear. I use the same code for applying the context view like I see in the JBehave examples today (org.jbehave.examples.core.CoreStories).
Does the ContextView still work in JBehave 4.0-beta-7?
Hans Schwäbli | 11 Jun 11:26 2014

Class which extends PerStoryWebDriverSteps is ignorerd if beforeStory() is overriden

Hello Mauro,
I extend a class from org.jbehave.web.selenium.PerStoryWebDriverSteps where I want to use the methode beforeStory() for some purpose.
But when I do this, the extension is not known anymore to JBehave when I start execution.
This is very strange to me. Just overriding the beforeStory() method in the class which extends PerStoryWebDriverSteps causes JBehave to ignore that class completely.
Maybe you can reproduce this or haven an idea how that occurs.
I can provide you a example which you can download from Github, but I haven't checked it in yet.
By the way, I use JBehave 4 beta 6 and jbehave-web-selenium 3.5.5.
Hans Schwäbli | 11 Jun 10:46 2014

NPE at org.jbehave.core.configuration.Configuration.doDryRun(Boolean)

Hello Mauro,
today I had a NullPointerException at org.jbehave.core.configuration.Configuration.doDryRun(Boolean) with JBehave beta-6.
It was because this.storyControls was null.
Why don't you use storyControls().doDryRun(dryRun) instead of this.storyControls.doDryRun(dryRun)?
Because the instance variable storyControls is lazy initialized in storyControls() method, so a NPE never could occur.
My workaround now is first to call storyControls() method and after that doDryRun(...)
Frank Pedroza | 10 Jun 16:59 2014

how to skip steps

Is it possible to skip single steps of a given story/scenario?  I don't think it is, but I'm wondering if there is a recommended approach.  I have a story with multiple scenarios and most of the scenarios can be fully automated.  However one of my scenarios has a few steps that really make more sense to be tested manually as they require some external party communication.  Would be awesome if I could maintain the same story and execute all but those steps.  Thoughts/suggestions?

Jonathan Gray | 10 Jun 10:53 2014

Error when running using Maven plugin


I'm currently seeing the following error when trying to run JBehave using 
the maven plugin against a Spring Batch project.

[ERROR] Failed to execute goal org.jbehave:jbehave-maven-plugin:3.9.2:run-
stories-as-embeddables (run-stories) on project mrp: Failed to run
 stories as embeddables: Failure in running embeddable: Hierarchy: Error 
creating bean with name 'hierarchyConfiguration': Invocation of ini
t method failed; nested exception is java.lang.NoClassDefFoundError: 
org/codehaus/jettison/mapped/Configuration: org.codehaus.jettison.mappe
d.Configuration -> [Help 1]

I currently only have one story (accompanied by Hierarchy Java class which 
is a JUnitStory).  This uses the SpringStepsFactory which in turns 
references an annotated HeirarchyConfiguration class for the context.

The jettison library is a transitive dependency from spring-batch-core and 
I can see it referenced in the first lines of INFO from the jbehave plugin 
(see below).  Is this a familiar problem to anyone?

[INFO] --- jbehave-maven-plugin:3.9.2:run-stories-as-embeddables (run-
stories)  <at>  mrp ---
[INFO] Running stories as embeddables using embedder Embedder
classes/, /C:/Dev/mrp/mrp/target/classes/, jbehave-core-3.9
.2.jar, junit-4.11.jar, hamcrest-core-1.3.jar, hamcrest-library-1.3.jar, 
hamcrest-integration-1.3.jar, commons-collections-3.2.1.jar, common
s-io-2.4.jar, commons-lang-2.6.jar, plexus-utils-3.0.10.jar, freemarker-
2.3.19.jar, paranamer-2.4.jar, xstream-1.4.5.jar, xmlpull-
r, xpp3_min-1.1.4c.jar, jbehave-spring-3.9.2.jar, spring-test-
4.0.5.RELEASE.jar, spring-context-4.0.5.RELEASE.jar, spring-aop-
jar, aopalliance-1.0.jar, spring-beans-4.0.5.RELEASE.jar, spring-core-
4.0.5.RELEASE.jar, commons-logging-1.1.3.jar, spring-expression-4.0.5.
RELEASE.jar, spring-jdbc-4.0.5.RELEASE.jar, spring-tx-4.0.5.RELEASE.jar, 
ojdbc7-, spring-batch-core-3.0.0.RELEASE.jar,
.jbatch-tck-spi-1.0.jar, javax.batch-api-1.0.jar, jettison-1.2.jar, spring-
batch-infrastructure-3.0.0.RELEASE.jar, spring-retry-1.1.0.RELEAS
E.jar, spring-batch-test-3.0.0.RELEASE.jar, hamcrest-all-
parent: s


To unsubscribe from this list, please visit:

Hans Schwäbli | 9 Jun 21:22 2014

Interview is online at JAXenter

Hello German speaking JBehave users!

I want to mention that there is an interview with Mauro Talevi now online:

In the upcoming Javamagazin edition there will be an article about JBehave. I think it will be published on the 2nd of July. It is a two part article, this will be part 1.
Corbin, J.D. | 3 Jun 18:36 2014

Maven Failsafe Plugin and JBehave

I am using the maven-failsafe-plugin (as opposed to the jbehave-maven-plugin) to run our JBehave integration tests.  I appears to run the test fine, but when there is an error it goes unreported.  I'm wondering if there are any others out there using the failsafe plugin with JBehave that might have some ideas why the errors are going unreported, or appear to be...

Russ Davidson | 3 Jun 13:57 2014

JBehave example fails to run tests when executed from Jenkins



I’m just looking to see if you’re able to help me with setting up the JBehave examples to be executed from Jenkins.


I have successfully run the examples within Eclipse, but copying over the exact same files/configuration and using the same libraries in Jenkins, the job successfully runs, but does not run any of the actual tests.


The only difference that I can see in the Jenkins console log is that surefire fails to find tests.

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) <at> jbehave.quickstart ---

[INFO] No tests to run.


The “No tests to run” message is not found in the Eclipse console log, where the tests are actually run.

(I have attached the console logs for both Eclipse and Jenkins, with and without the maven “-X” debug option)


I have used the jbehave-web-selenium-java-spring-archetype:3.5.5 (as the 3.6-beta-2 causes m2e errors) to create the project. The only change to the code is to use the “PropertyWebDriverProvider” instead of the default “FirefoxWebDriverProvider” in the etsy-steps.xml file, and passing the “-Dbrowser=htmlunit” maven option.


This works with Eclipse, but fails to run the tests with Jenkins.


JDK – 1.7.0_60

Maven – 3.2.1

Jenkins – 1.566

Eclipse – 4.3.2.v20140221-1852


Any help that you’re able to provide to get the tests working in Jenkins would be greatly appreciated.




Attachment ( application/x-zip-compressed, 71 KiB

To unsubscribe from this list, please visit:
Hans Schwäbli | 19 May 13:06 2014

saveScreenshotTo(String) returns boolean

This method returns a boolean:
What if it would return a File instead if it succeeds and null if it does not succeed?
Then the return value would contain more information and thus it would open up more possibilities. I then could more easily upload all these screenshots to a HP Quality test run. Currently it is hard to do this because all file names are like failed-scenario-1ab3b70f-f6d8-4dc8-a257-87a8c6a26276.png, I don't know which one belongs to which story or execution.
But if saveScreenshotTo(String) would return a File I could remember them and upload it after execution finished.
Well, its more nice to have, I know.