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

TestLink plugin indicates test case as "not run" and TestLink is not updated with build status

XMLWordPrintable

      version jenkins:1.565
      version testlink:1.9.10
      plugin testlink:3.10

      I just created a job to run an automated test, it allows you to run a file. ".bat" (display bonjour)

      when I run the build, it ends successfully but Testlink is not updated and testng-results.xml does not exist.

      I attached configuration Testlink and jenkins

        1. TEST-3200990b356a7000_samsung_GT-P5210.xml
          1 kB
        2. jenkins console.png
          jenkins console.png
          44 kB
        3. jenkins result.png
          jenkins result.png
          49 kB
        4. testlink.png
          testlink.png
          42 kB
        5. customer_field.png
          customer_field.png
          11 kB
        6. jenkins-conf1.png
          jenkins-conf1.png
          19 kB
        7. jenkins-conf2.png
          jenkins-conf2.png
          42 kB
        8. jenkins_console.png
          jenkins_console.png
          50 kB
        9. jenkins_results_testlink.png
          jenkins_results_testlink.png
          68 kB

          [JENKINS-23265] TestLink plugin indicates test case as "not run" and TestLink is not updated with build status

          mirou mirou created issue -

          Vincent Piet added a comment -

          Hi,

          Same problem here with JUnit test suites.

          I have :
          _Jenkins 1.567
          _TestLink Plugin 3.10
          _TestLink 1.9.10

          You will find enclosed screenshot and my JUnit report.

          Vincent Piet added a comment - Hi, Same problem here with JUnit test suites. I have : _Jenkins 1.567 _TestLink Plugin 3.10 _TestLink 1.9.10 You will find enclosed screenshot and my JUnit report.
          Vincent Piet made changes -
          Attachment New: jenkins console.png [ 26307 ]
          Attachment New: jenkins result.png [ 26308 ]
          Attachment New: TEST-3200990b356a7000_samsung_GT-P5210.xml [ 26309 ]
          Attachment New: testlink.png [ 26310 ]
          Vincent Piet made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]

          Robert Grzeskowiak added a comment -

          Hi,
          I had the same problem.
          After updating Jenkins to 1.572 problem doesn't occur anymore.

          Robert Grzeskowiak added a comment - Hi, I had the same problem. After updating Jenkins to 1.572 problem doesn't occur anymore.

          Robert Grzeskowiak added a comment -

          Problem still exists on Jenkins 1.576.

          Robert Grzeskowiak added a comment - Problem still exists on Jenkins 1.576.
          Robert Grzeskowiak made changes -
          Link New: This issue is duplicated by JENKINS-24424 [ JENKINS-24424 ]

          Vincent Piet added a comment -

          Hi, if someone is looking for integrate testlink in a CI project, have a look to https://code.google.com/p/testlink-api-java-client/

          It have been developed by the same person than the jenkins plugin. You will have to parse your result file (a JUnit test suit one in my case), and to send the results to testlink. Anyway it will work in a matter of minutes.

          Vincent Piet added a comment - Hi, if someone is looking for integrate testlink in a CI project, have a look to https://code.google.com/p/testlink-api-java-client/ It have been developed by the same person than the jenkins plugin. You will have to parse your result file (a JUnit test suit one in my case), and to send the results to testlink. Anyway it will work in a matter of minutes.

          Jes Kammer added a comment - - edited

          Still seem to be an issue in Jenkins 1.617

          From JUnitCaseClassNameResultSeeker.java:

          // Here we update testlink with our findings
for(Map.Entry<String, TestCaseWrapper> entry : classNameTestCase.entrySet()) {
	super.handleResult(entry.getValue(), build, listener, testlink, suiteResult);
}

          I am not sure this is the correct place, but is the code trying to update suiteResult. Should it be caseResult...

          Jes Kammer added a comment - - edited Still seem to be an issue in Jenkins 1.617 From JUnitCaseClassNameResultSeeker.java: // Here we update testlink with our findings for (Map.Entry< String , TestCaseWrapper> entry : classNameTestCase.entrySet()) { super .handleResult(entry.getValue(), build, listener, testlink, suiteResult); } I am not sure this is the correct place, but is the code trying to update suiteResult. Should it be caseResult...

          vishwamitra Mishra added a comment -

          Hi Any solution to this issue?

          vishwamitra Mishra added a comment - Hi Any solution to this issue?

            kinow Bruno P. Kinoshita
            mirou mirou mirou
            Votes:
            5 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: