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

Jenkins NUnit Plugin 0.14 incorrectly converts Unit XML results to JUnit

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • nunit-plugin
    • None
    • Windows Server 2003, Jenkins 1.497, Jenkins NUnit plugin 0.14, NUnit 2.6.2

      In the conversion of the NUnit XML results to JUnit, some tests are named incorrectly. When an NUnit output file contains a test-suite of type "TestFixture" containing a results element containing both test-suites of type "ParameterizedTest" and test-cases (not parameterized), the test-cases are reported with incorrect namespace and class names. It is as if some code were determining the namespace/class names to report by walking a certain number of tokens back in a fully qualified class name, and too many steps back are being taken for simple tests when parameterized tests are present.

      In TestResultLevel1.jpg all tests should appear under pacakge ASI.SOP.AmazonBTI.Tests. TestResultLevel3.jpg shows the badly parsed name AmazonUpcParseStrategyTests.ShouldRequireProductProgramFinder.

        1. ASI.SOP.AmazonBTI.Tests.xml
          19 kB
        2. JUnit-parameterized-simple.xml
          0.6 kB
        3. junitResult.xml
          22 kB
        4. NUnit-parameterized-simple.xml
          3 kB
        5. TestResultLevel1.jpg
          TestResultLevel1.jpg
          140 kB
        6. TestResultLevel2.jpg
          TestResultLevel2.jpg
          153 kB
        7. TestResultLevel3.jpg
          TestResultLevel3.jpg
          142 kB

            slide_o_mix Alex Earl
            dodren David Odren
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: