[
http://jira.codehaus.org/browse/JBEHAVE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210942#action_210942
]
Mauro Talevi commented on JBEHAVE-230:
--------------------------------------
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.
> Add Narrative elements to Story parsing
> ---------------------------------------
>
> Key: JBEHAVE-230
> URL: http://jira.codehaus.org/browse/JBEHAVE-230
> Project: JBehave
> Issue Type: Improvement
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 2.5
>
>
> 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").
--
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
