In Example class, replace new StoryReporterBuilder() with
new
StoryReporterBuilder().withCodeLocation(codeLocationFromClass(Example.class))
On 30/06/2014 22:55, Jonathan Gray wrote:
Attached is an example Maven project.
When I run the Example JUnitStory from within an IDE I can see that it
references <root>/target/jbehave rather than, what I would expect,
<root>/example-test/target/jbehave
I presume this is because the IDE thinks the root directory is <root>
However, the same is true for Maven. If I run mvn clean verify in the
root of the project then when executing the tests again it puts the
reports to <root>/target/jbehave
If the test has failed once then because I'm not using project
inheritence, but rather composition, then the parent/root is the last
thing to be cleaned so even if the test actually passes it will return
failure for the build. I presume its looking at the old failure.
Jon
On 23/06/2014 08:12, Mauro Talevi wrote:
Can you share a sample project with the configuration that you're using?
On 23/06/2014 00:56, Jonathan Gray wrote:
Hi,
I have a multi-module project which looks something
like the following (it happens to be Maven based).
project
- pom.xml
- app
+- pom.xml
- app-test
+- pom.xml
If I run "clean verify" against the project pom (it's not currently
using
inheritance from the parent) when it runs the maven plugin in the
app-test project I can see the following
[INFO] Generating reports view to 'C:\project\target\jbehave' ...
I would expect it to be generating to
C:\project\app-test\target\jbehave
Each of my Java tests are currently JUnitStory and running as
embeddables.
The configuration is using LoadFromClasspath(...) which works fine.
The stories run correctly but if they've already failed then at times
they
won't succeed because the target (parent) hasn't been cleaned.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
