JBehave

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: 3.0
• Component/s: Core
• Labels:

  None

PrintStreamStoryReporter and subclasses have the reportErrors flag that prints the failure stack trace. This is adequate but a rather crude approach.

In most use cases, we need to report the failure more meaningfully, be it an outcome failure or a system failure.

Issues to improve:

• show failure message after step and stack trace after entire scenario (only if failure trace flag is set)
• provide an outcomes table that allows to verify multiple outcomes and report them upon failure

Also ensure that the failure trace reporting is easily configurable via the StoryReporterBuilder.

• Assignee:

  Mauro Talevi

  Reporter:

  Mauro Talevi

• Created:

  05/Jun/10 1:22 PM

  Updated:

  12/Jun/10 8:16 AM

  Resolved:

  12/Jun/10 8:16 AM