Improve reporting of failure
----------------------------
Key: JBEHAVE-305
URL: http://jira.codehaus.org/browse/JBEHAVE-305
Project: JBehave
Issue Type: Improvement
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.0
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
assertion failure or a system failure.
Issues to address/review:
- show failure message and/or stacktrace after step or entire scenario?
- provide a table-based outcome output?
- provide ability to report a map of failed expected/actual outcomes?
Also ensure that a more verbose behaviour is configurable easily via the
StoryReporterBuilder.
--
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
