Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-561

after running test, when tests fail, it's hard to the find the failure reason

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.3
    • Fix Version/s: 2.13
    • Component/s: Maven Surefire Plugin
    • Labels:
      None

      Description

      Maven & surefire has been here for a while but still I'm missing this feature. When my tests fail, I'd like to know exact failure reason.

      1. Surefire summary does not show the stack trace / line number / assertion. Browsing results files in target dir is frustrating & time consuming.
      2. It is impossible to use surefire-report plugin in fully automated way. If I plug report-only goal to phase test, this goal is not executed when phase test fails

      Current workaround in my project is that every maven submodule has a handy batch file with 'mvn surefire-report:report-only'.

      One of the ways of implementing it is adding stacktrace/assertion information in test summary.

      What do you guys think about this idea?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                krosenvold Kristian Rosenvold
                Reporter:
                szczepiq@gmail.com Szczepan
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: