Hi,
Currently the timeout is global, not per story. If the docs suggest
otherwise, it was not intended. Correspondingly only a single
storyTimeoutInSecs parameter is provided.
Could you please create a JIRA issue detailing your usecase for the improvement
to make this story specific? How would you see it behaving and how would you
configure it? Please provide a concrete and realistic example of your usage.
Cheers
On 23 Jul 2014, at 19:24, Dan McLellan dmclel...@copyright.com wrote:
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
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
