Frank Pedroza | 1 Sep 19:12 2014
Picon

Story writing catalog

As we write more and more stories, we obviously accumulate a growing number of annotated step methods (currently we have ~350).  I'm wondering what do people do to more easily catalog the existing step methods so they don't duplicate steps as well as ensure they're taking advantage of the steps they've already written.  The eclipse plugin sort of helps with this, but it's hard to find that one method you're after when choosing from 350 options.
Anders | 1 Sep 19:10 2014
Picon

Where do I register for an account to access JBehave-Jira?

I’d like to be able to participate in the JBehave community, so how do I gain access to Jira?

 

/Anders

Chad Wilson | 20 Aug 22:23 2014
Picon

Steps classes question

Hello all,

I'm not sure if I'm missing something here.  According to the 
documentation in order to register Step class instances, an 
implementation of InjectableStepsFactory should be used.

Isn't there a way to scan the classpath for classes that are annotated 
with various step annotations?  Cucumber JVM supports this OOTB.

Chad

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Brent Barker | 11 Aug 18:10 2014
Picon

Report times are wrong when running multiple threads

Hi,
When executing reports in multiple threads, the execution times are not correct. Instead of varying from 1-10 minutes, they say the execute in microseconds (which i know is not the case)

Are other seeing this?
Thanks
-Brent
Dan McLellan | 23 Jul 20:24 2014

Are there plans to provide a story-specific timeout feature in JBehave?

Hi Everyone,

It looks, from issue 1436 of this site, that JBehave's current position is 
that the StoryTimeouts feature is intended for the execution of all test 
cases in a job, rather than each individual story being run:

Per Mario Talevi:

<excerpt>
As for the expected behaviour, do note that the story timeout is global, 
i.e. not per effective story execution time, in the sense that it's 
calculated (in "real" time) from the moment the execution of all stories 
starts.   After the elapsed time as reached the timeout, all story execution 
is cancelled.   We can try to improve on this for 4.0.
</excerpt>

Source: http://comments.gmane.org/gmane.comp.java.jbehave.user/1436

But the JBehave website itself seems to indicate that story-specific timeout 
control is already available in the current release, although the 
whereabouts of the class/methods to set those controls are not specified:

<excerpt from JBehave.org>
It is important to note that it's the entire story that is executed in one 
concurrent execution and that scenarios within the same story cannot be run 
concurrently. For each story execution a timeout in seconds can be set via 
the same configuration mechanism used to set the number of threads.
</excerpt from JBehave.org>

Source:
http://jbehave.org/reference/stable/multi-threading.html

But I can't find any methods or variables in Embedder, EmbedderControls, 
StoryReporter to set timeouts for individual stories, or any "watchdog" 
functionality in StoryManager (or elsewhere) to enforce them.

It would be good to know:
1.  Is story-specific execution timeout currently available, and if so, how 
can it be set?

2.  If you can't currently set the timeout on individual stories, is any 
such feature currently being targeted for 4.0 or another future release?

Thank you.

- Dan McLellan
Developer

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Brent Barker | 21 Jul 19:33 2014
Picon

Maping stories at the senario level

HI again,

I am using the story mapping feature with Maven. I am wondering if it is possible to map stories with meta tags at the scenario level, not only at the story level.

For example, I have a scenario inside of a story annotated with <at> bug. I'd like the map reports view to show that a scenario in the story has that <at> bug meta tag

Thanks in advance!
Brent Barker | 10 Jul 19:49 2014
Picon

Conditionally skip story using meta tag

Hi everyone!

Is there a easy way to conditionally skip a story using a meta tag? For example, I want to annotate my story with <at> bug BUG-3333 and then check if that bug is still open or not. If it is still open, skip the scenario/story.

Right now I am extending RegexStoryParser, calling super.ParseStory to get the story object, then if the bug meta property exists, I add the skip meta property to it. 

Is there a better way to do this? I am not sure how to feed a list of meta filters to the embedder, since I can not access it from the story configuration where I have access to the story object

Thanks
-Brent
Hans Schwäbli | 30 Jun 10:52 2014
Picon

Question regarding WebDriverScreenshotOnFailure

I have subclassed WebDriverScreenshotOnFailure and overridden afterScenarioFailure(UUIDExceptionWrapper).
 
I wondered why my class never was used. Then I discovered that I have to add the same annotation in the overriden method like it is in the superclass:
 
<at> AfterScenario(uponOutcome = Outcome.FAILURE)
 
Do you intend not to "inherit" this annotation to sub classes when afterScenarioFailure(UUIDExceptionWrapper) is overridden?
Brent Barker | 25 Jun 20:08 2014
Picon

Eclipse JBehave plugin - step method to story navigation

A feature that would be really nice and would give a huge advantage over other framework's plugins would be the ability to navigate from an annotated step method to the story/stories it is being used in. Currently I have only seen the ability to navigate from a story to a step.

Is this possible to do? 

Thanks 
-Brent
Brent Barker | 24 Jun 01:24 2014
Picon

Configuring Threads in pom.xml

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>
  <phase>integration-test</phase>
  <configuration>
    <scope>test</scope>
    <ignoreFailureInStories>true</ignoreFailureInStories>
    <ignoreFailureInView>false</ignoreFailureInView>
    <threads>4</threads>
    <includes>
      <include>**/WeldAnnotatedStoryRunner.java</include>
    </includes>
  </configuration>
  <goals>
    <goal>run-stories-with-annotated-embedder</goal>
  </goals>
</execution>

Is there something I am missing here?

Thanks in advance!
-Brent 
Jonathan Gray | 23 Jun 00:56 2014
Picon

Specifying report path in multi-module project

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


Gmane