JBehave
  1. JBehave
  2. JBEHAVE-305

Improve reporting of failure

          Details

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

            Description

            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.

              Activity

              Mauro Talevi made changes -
              Field Original Value New Value
              Status Open [ 1 ] In Progress [ 3 ]
              Mauro Talevi made changes -
              Description 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.

                              		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.

               
              Mauro Talevi made changes -
              Status In Progress [ 3 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]

                People

                • Assignee:
                  Mauro Talevi
                  Reporter:
                  Mauro Talevi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: