• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • junit-plugin
    • None
    • Platform: All, OS: All

      A make integration test with the failsafe-maven-plugin, but test result are not
      aggregated with unit surefire-reports.

      It's where a nice feature !!!

      Thanks Steph

          [JENKINS-4229] Support failsafe-reports

          Sean Flanigan added a comment -

          Just thought I'd link to a bit of development discussion I found here here: http://markmail.org/thread/blltzav2z3lwyssr

          Sean Flanigan added a comment - Just thought I'd link to a bit of development discussion I found here here: http://markmail.org/thread/blltzav2z3lwyssr

          vvilhonen added a comment - - edited

          Hi,

          I attached a simple patch, which seemed to do the trick for me. Could you merge it in to the source tree?

          -Vesa

          vvilhonen added a comment - - edited Hi, I attached a simple patch, which seemed to do the trick for me. Could you merge it in to the source tree? -Vesa

          mohlendo added a comment -

          Any ideas when this will be fixed?

          mohlendo added a comment - Any ideas when this will be fixed?

          Code changed in hudson
          User: : kohsuke
          Path:
          branches/rc/maven-plugin/src/main/java/hudson/maven/reporters/SurefireArchiver.java
          trunk/www/changelog.html
          http://jenkins-ci.org/commit/35445
          Log:
          [FIXED JENKINS-4229] Supported failsafe reports for the Maven2 job type.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: branches/rc/maven-plugin/src/main/java/hudson/maven/reporters/SurefireArchiver.java trunk/www/changelog.html http://jenkins-ci.org/commit/35445 Log: [FIXED JENKINS-4229] Supported failsafe reports for the Maven2 job type.

          I'm sorry this patch took so long to apply.

          Kohsuke Kawaguchi added a comment - I'm sorry this patch took so long to apply.

          dogfood added a comment -

          Integrated in hudson_main_trunk #314

          dogfood added a comment - Integrated in hudson_main_trunk #314

          kutzi added a comment -

          I wonder what's the reasoning behind this line in the patch:

          if (!mojo.is("org.apache.maven.plugins", "maven-failsafe-plugin", "integration-test")) {
             // tell surefire:test to keep going even if there was a failure,
             ...
          

          i.e. why should failsafe tests NOT go on if a test failure is detected? Why should they behave differently than 'normal' surefire tests?
          (Note: seem that the integration-tests goal doesn't suppport the testFailureIgnore parameter directly. One would have to intercept the verify goal of the plugin)

          kutzi added a comment - I wonder what's the reasoning behind this line in the patch: if (!mojo.is("org.apache.maven.plugins", "maven-failsafe-plugin", "integration-test")) { // tell surefire:test to keep going even if there was a failure, ... i.e. why should failsafe tests NOT go on if a test failure is detected? Why should they behave differently than 'normal' surefire tests? (Note: seem that the integration-tests goal doesn't suppport the testFailureIgnore parameter directly. One would have to intercept the verify goal of the plugin)

          Mark Hudson added a comment -

          Did Failsafe integration test reporting go away? Or get absorbed into another plugin? I can't find anything at https://wiki.jenkins-ci.org/dosearchsite.action?queryString=failsafe

          Mark Hudson added a comment - Did Failsafe integration test reporting go away? Or get absorbed into another plugin? I can't find anything at  https://wiki.jenkins-ci.org/dosearchsite.action?queryString=failsafe

            Unassigned Unassigned
            scusin scusin
            Votes:
            24 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: