Re: [jbehave-user] Specifying report path in multi-module project

2014-06-23 Thread Mauro Talevi

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




Re: [jbehave-user] Excluding - in meta filters

2014-06-23 Thread Brent Barker
That worked, Thanks!


On Sat, Jun 21, 2014 at 9:45 AM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:

 You can use -bug JBEHAVE*281.

 Or use the Groovy Matcher

 http://jbehave.org/reference/stable/meta-filtering.html


 On 18/06/2014 00:28, Brent Barker wrote:

 I have a meta filter on a story similar to this:

 Meta:
 @bug JBEHAVE-281

 The issue is when I try to filter on that, using

 -bug JBEHAVE-281

 it does not match, but only matches to similar items when I do

 -bug JBEHAVE*


 Is there a way to escape the dash in the meta filter so I can filter for
 that specific bug?

 Thanks!
 -Brent



 -
 To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email





[jbehave-user] Configuring Threads in pom.xml

2014-06-23 Thread Brent Barker
Hi
I'm trying to configure the number of threads to run via maven, however the
number of threads does not seem to be picked up. If i directly edit the
annotation in WeldAnnotatedStoryRunner, I am able to get the tests to run
with multiple threads.


Here is my configuration:
execution
  phaseintegration-test/phase
  configuration
scopetest/scope
ignoreFailureInStoriestrue/ignoreFailureInStories
ignoreFailureInViewfalse/ignoreFailureInView
threads4/threads
includes
  include**/WeldAnnotatedStoryRunner.java/include
/includes
  /configuration
  goals
goalrun-stories-with-annotated-embedder/goal
  /goals
/execution

Is there something I am missing here?

Thanks in advance!
-Brent