[
http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-156:
---------------------------------
Description:
In order to avoid the need to define a Java class for each textual story
As a story runner
I want to be able to run multiple textual stories from the same Java entry
point, provided all stories use the same StoryConfiguration and the same
CandidateSteps.
was:
I want to be able to run multiple textual stories from the same Java
RunnableStory, provided they use the same StoryConfiguration and the same
CandidateSteps instances.
This would avoid the need to define a Java RunnableStory class for each textual
story.
Affects Version/s: (was: 2.0)
Summary: Allow running of multiple textual stories using a single
Java entry point (was: Allow running of multiple textual stories using a
single Java RunnableStory )
> Allow running of multiple textual stories using a single Java entry point
> -------------------------------------------------------------------------
>
> Key: JBEHAVE-156
> URL: http://jira.codehaus.org/browse/JBEHAVE-156
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 3.0
>
>
> In order to avoid the need to define a Java class for each textual story
> As a story runner
> I want to be able to run multiple textual stories from the same Java entry
> point, provided all stories use the same StoryConfiguration and the same
> CandidateSteps.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
