Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51347

Test Status "notrun" being reported as "failed" test

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • xunit-plugin
    • None
    • Jenkins: 1.
      xunit-plugin: 1.104
      Ubuntu 14.04
      Java: 1.7

      We're running tests through ctest. Test engine is googletest

      We "disable" tests through prefixing tests with "DISABLED"

      Those test are not run, and the status field is as such "<Test Status="notrun">"

      However, this status is reported as a failed test through the xunit plugin. This isn't a failed test for us.

      The xunit-plugin choice used to report test results is "CTest-Version N/A"

        1. snippet_test_report_file.txt
          4 kB
          David Joo
        2. Test_2.xml
          4 kB
          David Joo

          [JENKINS-51347] Test Status "notrun" being reported as "failed" test

          Nikolas Falco added a comment -

          Please attach report files

          Nikolas Falco added a comment - Please attach report files

          Nikolas Falco added a comment - - edited

          Thank for the second complete test report file (Test_2.xml). It is useful because it prevents a bug in the duration.

          Nikolas Falco added a comment - - edited Thank for the second complete test report file (Test_2.xml). It is useful because it prevents a bug in the duration.

          Code changed in jenkins
          User: Nikolas Falco
          Path:
          src/main/java/org/jenkinsci/plugins/xunit/types/CTest.java
          src/main/java/org/jenkinsci/plugins/xunit/types/CTestInputMetric.java
          src/main/java/org/jenkinsci/plugins/xunit/types/CTestType.java
          src/main/resources/org/jenkinsci/plugins/xunit/types/ctest-to-junit.xsl
          src/test/java/org/jenkinsci/plugins/xunit/types/CTestTest.java
          src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase1/result.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase2/result.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase3/input.xml
          src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase3/result.xml
          http://jenkins-ci.org/commit/xunit-plugin/dd79be01562d8f6c679ef42c7f86a575511d9f7f
          Log:
          JENKINS-51347 Test Status "notrun" being reported as "failed" test

          Fix XSL to not include in failure count also skipped tests.

          *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

          Functionality will be removed from GitHub.com on January 31st, 2019.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nikolas Falco Path: src/main/java/org/jenkinsci/plugins/xunit/types/CTest.java src/main/java/org/jenkinsci/plugins/xunit/types/CTestInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/CTestType.java src/main/resources/org/jenkinsci/plugins/xunit/types/ctest-to-junit.xsl src/test/java/org/jenkinsci/plugins/xunit/types/CTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase1/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase2/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase3/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase3/result.xml http://jenkins-ci.org/commit/xunit-plugin/dd79be01562d8f6c679ef42c7f86a575511d9f7f Log: JENKINS-51347 Test Status "notrun" being reported as "failed" test Fix XSL to not include in failure count also skipped tests. * NOTE: * This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.

          David Joo added a comment -

          Thanks for the fix.

          Will we see the changed take effect when version 1.105 is released in the future?

          David Joo added a comment - Thanks for the fix. Will we see the changed take effect when version 1.105 is released in the future?

            nfalco Nikolas Falco
            d8v1dee David Joo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: