Hi Marius,
that is certainly possible. Could you raise a jira issue describing
your use case in more detail?
Cheers
On 01/07/2012 19:31, Marius Brot wrote:
Hi Mauro,
what I'm searching for is something like meta data on steps level.
Similar to the meta data on story or scenario level.
The JBehave Web Runner looks great and maybe we can enhance it to
fulfill the requirements.
Extending the Stepdoc or StepCandidate class with custom informations
would maybe achieve my needs - if I can push them up to the Web Runner
pages.
What do you think?
Cheers
Marius
On 01/07/2012 17:54, Mauro Talevi wrote:
Hi Marius,
the issue you pose is an important one.
JBehave provides information about available steps via Stepdocs:
http://jbehave.org/reference/stable/finding-steps.html
These stepdocs can be generated in different ways, via command-line (via
Ant or Maven) or programmatically.
You can easily write a wrapper to generate and publish them as artifacts
for each component.
Here's an example of stepdocs generation using Maven:
https://github.com/jbehave/jbehave-core/tree/master/examples/trader-stepdocs
The JBehave Web Runner also provides a web-interface to these steps
(with auto-search functionality):
http://jbehave.org/reference/web/stable/using-web-runner.html
Hope this satisfies your requirements. If not, please feel free to
suggest new or improved functionality. We are always driven by users'
requirements.
Cheers
On 01/07/2012 14:03, Marius Brot wrote:
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
