[
http://jira.codehaus.org/browse/JBEHAVE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-471 started by Mauro Talevi.
> Show as pending in reports view scenarios and stories that contain pending
> steps or no steps
> --------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-471
> URL: http://jira.codehaus.org/browse/JBEHAVE-471
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 3.4
>
>
> As suggested by Jonathan Woods on user list:
> "It would be useful if
> (i) stories with no steps were reported as pending, and their constituent
> scenarios too
> (ii) stories with any pending steps were reported as pending, and their
> constituent scenarios too
> (iii) a run with any pending stories was itself reported as pending, even if
> it was also regarded as successful
> When I say 'reported as', I mean in the kind of end result you can see at
> target/jbehave/view/reports.html. In jbehave-trader-example, I tried adding
> a new story alongside the existing test stories, and of course it was
> reported, but as successful only - nothing to indicate there's no
> implementation as suggested in (i) above.
> This kind of behaviour would serve as a flag to keep the implementer honest
> and maintain the flow of top-down development: you've not implemented x if
> you've not implemented something x depends on. It would help keep story
> development and implementation in synch: if I make a modification to a story
> (or create a whole new story) and JBehave can tell me everywhere that
> implementation is pending, that's great."
--
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
