Hi Dan,
We achieve this by having an AbstractStory extending JUnitStory
in which we provided a protected getStoryTimeout() that returns a
DEFAULT_TIMEOUT. Whenever we want a different timeout we override the
getStoryTimeout()
method from in the ConcreteStory.
Then in our bootstrapping custom
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
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
