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 Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.3
    • Fix Version/s: 2.13
    • Component/s: Maven Surefire Plugin
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      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?

        Issue Links

          Activity

          Hide
          Benjamin Bentmann added a comment -

          1. Surefire summary does not show the stack trace / line number / assertion. Browsing results files in target dir is frustrating & time consuming.

          And you already tried setting the plugin's parameter useFile to false?

          Show
          Benjamin Bentmann added a comment - 1. Surefire summary does not show the stack trace / line number / assertion. Browsing results files in target dir is frustrating & time consuming. And you already tried setting the plugin's parameter useFile to false?
          Hide
          Szczepan Faber added a comment -

          No I haven't - it didn't occur me at all that this option can be any helpful. Thanks for the hint!

          Anyway, I will see how useful it is and get back.

          Show
          Szczepan Faber added a comment - No I haven't - it didn't occur me at all that this option can be any helpful. Thanks for the hint! Anyway, I will see how useful it is and get back.
          Hide
          james strachan added a comment -

          I think this issue is mostly resolved now - though it would be nice to be able to turn off useFile from the command line like this related issue

          Show
          james strachan added a comment - I think this issue is mostly resolved now - though it would be nice to be able to turn off useFile from the command line like this related issue
          Hide
          Alexander Klimetschek added a comment -

          For working with the file reports, have a look at SUREFIRE-701 - it provides a showSuccess=false option that simply omits successful reports. Together with disableXmlReport=true to get rid of the xml files in target/surefire-reports, very useful when you develop & only look for the failed test reports.

          Show
          Alexander Klimetschek added a comment - For working with the file reports, have a look at SUREFIRE-701 - it provides a showSuccess=false option that simply omits successful reports. Together with disableXmlReport=true to get rid of the xml files in target/surefire-reports, very useful when you develop & only look for the failed test reports.
          Hide
          Kristian Rosenvold added a comment -

          Fixed with greatly improved summary display

          Show
          Kristian Rosenvold added a comment - Fixed with greatly improved summary display

            People

            • Assignee:
              Kristian Rosenvold
              Reporter:
              Szczepan Faber
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: