A tree-based story runner that separates creation of performable steps from execution

Description

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.

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created May 8, 2012 at 1:30 PM
Updated May 29, 2015 at 2:30 PM
Resolved May 29, 2015 at 2:30 PM

Flag notifications