Details
-
Type:
New Feature
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.5
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
The current domain model captures everything before the first Scenario as unstructured text (hence the name Blurb in the domain module). Hence not an issue in a plain text report (newlines are maintained) but becomes less readable in, say, HTML.
We should add an optional Narrative element with appropriate keywords, so as to be able to distinguish between the various elements of the narrative ("In order to", "As a", "I want to").
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Mauro Talevi [ maurotalevi ] |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Mauro Talevi
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
Mauro Talevi
made changes -
| Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
Added keyword-driven optional narrative elements to story. Keywords are (i18n-able as all keywords):
Narrative:
In order to [the story value]
As a [the actor(s)]
I want to [the story objective]
Reports have been updated to be narrative-aware. HTML reports are CSS-styleable.
Trader example scenarios updated to use narratives - not all scenarios to show its optional nature.