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

testlink plugin can't find test results in testng-results.xml

    XMLWordPrintable

Details

    Description

      We’re experiencing troubles with integrating the Jenkins and testlink. Is seems that Jenkins does not update testlink with it’s test result.

      Attachements :
      1. Testing-results.xml – this is the end results that Jenkins is configured to scan.
      2. Screen capture of testlink testcase
      3. Screen capture of Jenkins configuration.

      I did everything according to the tutorial but still I don’t see testlink updating .

      You can also see a part of the log Jenkins provide :

      “Found 1 automated test cases in TestLink.

      Sorting automated test cases by TestLink test plan execution order.

      Executing single Build Steps.

      TestNG Reports Processing: START
      Looking for TestNG results report in workspace using pattern: /root/.jenkins/workspace/FormHttpFlowTest/qa/scripts/webnode/selenium/FormHttpFlowTest/test-output/testng-results.xml
      Saving reports...
      Processing '/root/.jenkins/jobs/FormHttpFlowTest/builds/2012-08-28_10-18-18/testng/testng-results.xml'
      TestNG Reports Processing: FINISH
      Executing iterative Build Steps.

      Looking for the test results of TestLink test cases.

      Looking for test results in TestNG suites.

      Looking for test results in TestNG suites.

      Found 0 test result(s).”

      Jenkins version: 1.478

      Testlink version: 1.9.1

      Attachments

        1. jenkins.jpg
          jenkins.jpg
          124 kB
        2. JENKINS-14954-001.png
          JENKINS-14954-001.png
          84 kB
        3. JENKINS-14954-002.png
          JENKINS-14954-002.png
          110 kB
        4. JENKINS-14954-003.png
          JENKINS-14954-003.png
          102 kB
        5. JENKINS-14954-004.png
          JENKINS-14954-004.png
          91 kB
        6. JENKINS-14954-005.png
          JENKINS-14954-005.png
          110 kB
        7. JENKINS-14954-006.png
          JENKINS-14954-006.png
          81 kB
        8. testlink.jpg
          testlink.jpg
          36 kB
        9. testng-results.xml
          3 kB

        Issue Links

          Activity

            Hello!

            Sorry for the delayed response. The TestNG XML pattern is relative to the workspace. Could you give it a try, maybe using FormHttpFlowTest/qa/scripts/webnode/selenium/**/testng-results.xml or a similar pattern.

            Cheers, Bruno

            kinow Bruno P. Kinoshita added a comment - Hello! Sorry for the delayed response. The TestNG XML pattern is relative to the workspace. Could you give it a try, maybe using FormHttpFlowTest/qa/scripts/webnode/selenium/**/testng-results.xml or a similar pattern. Cheers, Bruno
            jacobk jacob koren added a comment -

            There is no problem for jenkins to find the file, the problem happens when it parse the file and does not find results to send to testlink ...

            jacobk jacob koren added a comment - There is no problem for jenkins to find the file, the problem happens when it parse the file and does not find results to send to testlink ...

            Hi Jacob!

            I believe I didn't make myself clear, sorry.

            You have a single build step, that publishes TestNG reports. That build step finds your TestNG report. As below:

            >Executing single Build Steps.
            >TestNG Reports Processing: START
            >Looking for TestNG results report in workspace using pattern: >/root/.jenkins/workspace/FormHttpFlowTest/qa/scripts/webnode/selenium/FormHttpFlowTest/test-output/testng->results.xml
            >Saving reports...
            >Processing '/root/.jenkins/jobs/FormHttpFlowTest/builds/2012-08-28_10-18-18/testng/testng-results.xml'
            >TestNG Reports Processing: FINISH

            However, there is another step that invokes the result seeking strategies that you've configured. This step needs paths & patterns relative to the workspace (I'm adding this to the help button next to the include pattern field in the UI).

            I've attached some screenshots that may help to illustrate what has been done. The TestNG XML file is the one that you uploaded here (that always helps when debugging issues, thanks a lot). Basically, I edited my project and changed the include pattern from /home/kinow/.../jobs/<job>/workspace/testng-results.xml to **/testng-results.xml

            Let me know if that helps,
            Bruno

            kinow Bruno P. Kinoshita added a comment - Hi Jacob! I believe I didn't make myself clear, sorry. You have a single build step, that publishes TestNG reports. That build step finds your TestNG report. As below: >Executing single Build Steps. >TestNG Reports Processing: START >Looking for TestNG results report in workspace using pattern: >/root/.jenkins/workspace/FormHttpFlowTest/qa/scripts/webnode/selenium/FormHttpFlowTest/test-output/testng->results.xml >Saving reports... >Processing '/root/.jenkins/jobs/FormHttpFlowTest/builds/2012-08-28_10-18-18/testng/testng-results.xml' >TestNG Reports Processing: FINISH However, there is another step that invokes the result seeking strategies that you've configured. This step needs paths & patterns relative to the workspace (I'm adding this to the help button next to the include pattern field in the UI). I've attached some screenshots that may help to illustrate what has been done. The TestNG XML file is the one that you uploaded here (that always helps when debugging issues, thanks a lot). Basically, I edited my project and changed the include pattern from /home/kinow/.../jobs/<job>/workspace/testng-results.xml to **/testng-results.xml Let me know if that helps, Bruno

            Code changed in jenkins
            User: Bruno P. Kinoshita
            Path:
            src/main/java/hudson/plugins/testlink/result/JUnitCaseNameResultSeeker.java
            src/main/java/hudson/plugins/testlink/result/JUnitMethodNameResultSeeker.java
            src/main/java/hudson/plugins/testlink/result/TestNGMethodNameDataProviderNameResultSeeker.java
            src/main/java/hudson/plugins/testlink/result/TestNGMethodNameResultSeeker.java
            src/main/resources/hudson/plugins/testlink/util/Messages.properties
            src/main/resources/hudson/plugins/testlink/util/Messages_en.properties
            src/main/resources/hudson/plugins/testlink/util/Messages_pt.properties
            src/main/webapp/help-junitIncludePattern.html
            src/main/webapp/help-junitIncludePattern_es.html
            src/main/webapp/help-junitIncludePattern_fr.html
            src/main/webapp/help-junitIncludePattern_pt.html
            src/main/webapp/help-tapIncludePattern.html
            src/main/webapp/help-tapIncludePattern_es.html
            src/main/webapp/help-tapIncludePattern_fr.html
            src/main/webapp/help-tapIncludePattern_pt.html
            src/main/webapp/help-testNGIncludePattern.html
            src/main/webapp/help-testNGIncludePattern_es.html
            src/main/webapp/help-testNGIncludePattern_fr.html
            src/main/webapp/help-testNGIncludePattern_pt.html
            http://jenkins-ci.org/commit/testlink-plugin/2c5ea35e32d6b4614b35fad0b21a0a24fdfa55a6
            Log:
            JENKINS-14954 Added note about requirement to have the include patterns
            relative to the job workspace. Also fixed the log messages for result
            seeking strategies.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/testlink/result/JUnitCaseNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/JUnitMethodNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TestNGMethodNameDataProviderNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TestNGMethodNameResultSeeker.java src/main/resources/hudson/plugins/testlink/util/Messages.properties src/main/resources/hudson/plugins/testlink/util/Messages_en.properties src/main/resources/hudson/plugins/testlink/util/Messages_pt.properties src/main/webapp/help-junitIncludePattern.html src/main/webapp/help-junitIncludePattern_es.html src/main/webapp/help-junitIncludePattern_fr.html src/main/webapp/help-junitIncludePattern_pt.html src/main/webapp/help-tapIncludePattern.html src/main/webapp/help-tapIncludePattern_es.html src/main/webapp/help-tapIncludePattern_fr.html src/main/webapp/help-tapIncludePattern_pt.html src/main/webapp/help-testNGIncludePattern.html src/main/webapp/help-testNGIncludePattern_es.html src/main/webapp/help-testNGIncludePattern_fr.html src/main/webapp/help-testNGIncludePattern_pt.html http://jenkins-ci.org/commit/testlink-plugin/2c5ea35e32d6b4614b35fad0b21a0a24fdfa55a6 Log: JENKINS-14954 Added note about requirement to have the include patterns relative to the job workspace. Also fixed the log messages for result seeking strategies.

            Fixed in 3.1.7 (available from update-center in the next hours)

            kinow Bruno P. Kinoshita added a comment - Fixed in 3.1.7 (available from update-center in the next hours)
            jacobk jacob koren added a comment -

            Great, Tnx!!!

            jacobk jacob koren added a comment - Great, Tnx!!!

            People

              kinow Bruno P. Kinoshita
              jacobk jacob koren
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: