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.