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

ResultSeeking Strategy "jUnit Suite Name" not working

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • testlink-plugin
    • None
    • Jenkins 1.516 on Debian

      We use CasperJS as Tool for Frontend Integrationtests. Casper generates jUnit-Files like this:

      <testsuites time="12.975">
      <testsuite name="/qa/src/test/javascript/portal/questionnaire/photoupload.js" tests="2" failures="0" errors="0" time="12.975" timestamp="2013-11-01T13:24:46.696Z" package="../../test/javascript/portal/questionnaire/photoupload">
      <testcase name="ProfilePrefill is openend" classname="../../test/javascript/portal/questionnaire/photoupload" time="10.292"/>
      <testcase name="ajaxTransport is defined" classname="../../test/javascript/portal/questionnaire/photoupload" time="0.001"/>

      <system-out/>
      </testsuite>
      </testsuites>

      The only way I see to get a mapping is via the ResultSeeking Strategy: "jUnit Suite Name".
      We use exactly the String that is entered in Testlinks "Custom Field"

      We also tried to use a simpler name="photoupload".

      Jenkins can read the jUnit File and shows the correct Result. But for Testlink "Execution Status" is set to "Not Run"

      We have other Backend jUnit Testfiles that do work for us. (At least with ResultSeeking "jUnit Method Name")

          [JENKINS-20381] ResultSeeking Strategy "jUnit Suite Name" not working

          Florian Weber added a comment -

          The logfile is not very helpful:

          [32mDone, without errors.
          Looking for the test results of TestLink test cases.

          Looking for test results in JUnit methods by its name.

          Found 1 test result(s).

          [xUnit] [INFO] - Starting to record.
          [xUnit] [INFO] - Processing JUnit
          [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'qa/src/main/grunt/xunit/*/.xml' relative to '/parship/jenkins/workspace/Testlink_frontend' for the testing framework 'JUnit'.

          ---------------
          One Testresult is found but nothing updated in Testlink here

          Florian Weber added a comment - The logfile is not very helpful: [32mDone, without errors. Looking for the test results of TestLink test cases. Looking for test results in JUnit methods by its name. Found 1 test result(s). [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'qa/src/main/grunt/xunit/* / .xml' relative to '/parship/jenkins/workspace/Testlink_frontend' for the testing framework 'JUnit'. --------------- One Testresult is found but nothing updated in Testlink here

          Bruno P. Kinoshita added a comment -

          Hi, I've successfully reproduced the issue.

          Somewhere from 1.40x till the current Jenkins release the test suite name is now escaped. /'s and other chars are replaced (see SuiteResult class).

          I'm taking a look at different options to see how we can circumvent this.

          Bruno

          Bruno P. Kinoshita added a comment - Hi, I've successfully reproduced the issue. Somewhere from 1.40x till the current Jenkins release the test suite name is now escaped. /'s and other chars are replaced (see SuiteResult class). I'm taking a look at different options to see how we can circumvent this. Bruno

          Bruno P. Kinoshita added a comment -

          Hi, unfortunately the only way to fix it will be to write a new parser to get the suite name without being escaped.

          That might take a few days until I fix it and release a new version, but hopefully by next week or so we'll have a 3.9 with this issue fixed

          Thanks for reporting.
          Bruno

          Bruno P. Kinoshita added a comment - Hi, unfortunately the only way to fix it will be to write a new parser to get the suite name without being escaped. That might take a few days until I fix it and release a new version, but hopefully by next week or so we'll have a 3.9 with this issue fixed Thanks for reporting. Bruno

          Florian Weber added a comment -

          I just wanted to ask if you have any news on this issue.

          Thanks
          Florian

          Florian Weber added a comment - I just wanted to ask if you have any news on this issue. Thanks Florian

          Bruno P. Kinoshita added a comment -

          Hi, not yet. I have to submit a pull request to Jenkins core, to get the suite name back and update the plug-in code as well. Unfortunately I don't think I can do that before holidays. Feel free to submit a pull request or update this issue with other suggestions.

          Thanks Florian
          Bruno

          Bruno P. Kinoshita added a comment - Hi, not yet. I have to submit a pull request to Jenkins core, to get the suite name back and update the plug-in code as well. Unfortunately I don't think I can do that before holidays. Feel free to submit a pull request or update this issue with other suggestions. Thanks Florian Bruno

            kinow Bruno P. Kinoshita
            fwebdev Florian Weber
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: