The application under test contains several different functional modules to
test.
These modules are tested by different testers.
Currently, if a tester writes a JBehave story, the story editor proposes
all steps which exist for all modules.
Is it possible to restrict which steps are proposed in
Great idea, thank you!
As it seems the JBehave editor uses the input from the JUnitStory class.
We will try your solution.
2014-02-05 Bernardo Pinto bernardo.pi...@byclosure.com:
Yes, it is.
Each one of your class that represents a story can extend JUnitStory.
If you override the
More generally, you could extend JUnitStories to provide a common configuration
and steps context to different set of stories.
On 5 Feb 2014, at 11:29, Hans Schwäbli bugs.need.love@gmail.com wrote:
Great idea, thank you!
As it seems the JBehave editor uses the input from the
