First of all: I like JBehave, but is it usable/operational for bigger
projects?
The big question for me is: How do you manage your documentation stuff
about the available steps?
I will illustrate our project structure to eplain why I'm asking.
We have multiple components under test. Each component is probably an
own application. For each component we created a JBehave project which
implements its own Steps.
A manager project will collect them all together and executes the stories.
that means:
- Component A lib: Project with Component A related Steps
- Component B lib: Project with Component B related Steps
- ... and so on
- Test Manager: brings all component "libraries" together and contains
the Stories for execution.
-------
How could we provide the story writers information about all available
steps? Any ideas, best practices... ?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
