Details
Description
As suggested by Jonathan Woods on user list:
"It would be useful if
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 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."
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Fix Version/s | 3.3.1 [ 17301 ] |
The stories are now reported as pending if they contains scenarios, which in turn are pending if the contain pending steps.
The pending stories and scenarios are reported both in the reports (using same colour coding of pending steps) and in the command-line execution.