[
https://jira.codehaus.org/browse/JBEHAVE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298157#comment-298157
]
Mauro Talevi commented on JBEHAVE-777:
--------------------------------------
Hi Brian,
committed and pushed a first refactor in jbehave-4.x branch
(https://github.com/jbehave/jbehave-core/tree/jbehave-4.x).
Introduced a PerformanceTree in place of StoryRunner. The behaviour is
backward compatible with exception of CrossReference which implicitly relies on
the step generation and execution to be done at same time. In any case,
removing CrossReference is one of the objectives of this refactor as the result
tree will be serialisable.
> A tree-based story runner that separates creation of performable steps from
> execution
> --------------------------------------------------------------------------------------
>
> Key: JBEHAVE-777
> URL: https://jira.codehaus.org/browse/JBEHAVE-777
> Project: JBehave
> Issue Type: New Feature
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 4.x
>
>
> In 3.x the StoryRunner creates and executes the steps for each story and
> scenario while keeping state.
> We want to separate the creation of performable steps from their execution
> and build a tree of performable objects. The state should not be held any
> more as a member variable but in a shared run context.
> The result of execution of the performable tree should be serialisable and
> consumable by any reporting/UI layer independent of the StoryReporters.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
