Stories consist of Actions and Events are created as a result of Actions running. The chain of Actions and Events set off by a run is called a Story Run. Story Runs can consist of unlimited amounts of Actions and are recorded with a unique globally unique identifier for each chain of Events that occurs. The unique identifier of the Story Run can be utilized by using the Story Run Widgets.
When reviewing events from a Story, the Story Runs view can be utilized to present a clear picture of events as they took place during an execution route.
Story Run View
The Story Run view can be accessed by using the "Story Runs" option located at the top of any Story.
The Story Runs view displays the result of any Story Run which are listed by descending starting time on the left side of the page.
Clicking on a Story Run will display all Actions and their associated Events which took place during that Story Run in the Routes panel immediately to the right of Story Runs. At the bottom of the Routes panel will list the number of Events which took place across the number of Actions, when the Story Run began, when the Story Run finished, and the difference between the beginning and end time.
Clicking on an Event within the Route panel will display the event in the next panel to the right along with all preceding and/or succeeding events. This provides a single view of the details of all Events in a Route.
Events can take multiple Routes during a single Story Run, usually as a result of "exploding" an array or branching to multiple Actions in a Story. When an individual Event is selected in the Routes pane, the Events that were a part of that particular will remain highlighted while Events not part of that particular Route will be dulled making it easier to understand which events took place to arrive at a particular Event.
View and Edit Actions from Story Runs
Clicking on the Action title of any of the Events seen in the primary Event viewer will bring up an editor panel to the immediate right. This panel allows for viewing and configuring of Actions as they currently exist. This is helpful when editing Action configuration while referencing a wide range of Event data from previous Story Runs.