• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • testlink-plugin
    • Jenkins ver. 1.474
      TestLink 1.9.8 (Lobizon)
      Jenkins TestLink Plugin 3.7

      I configured a sample testlink test plan that includes an automatic test.
      In TestLink "Test Plan Management" the value "Test Case Qty" is not zero.
      I configured a sandbox job, see attachment config.xml.
      During the execution (see log attached) it says me that no atomated test cases is found in TestLink.
      What is going wrong?

        1. config.xml
          3 kB
        2. log
          2 kB

          [JENKINS-20339] Found 0 automated test cases in TestLink

          I have this problem, too. But I found out, that if you execute the test case manually in testlink (just create a build, click "test executing" and mark each test case in your test plan as "ok"), the testlink plugin gets all the test cases from the plan with the next run of the jenkins job.

          Sascha Bartels added a comment - I have this problem, too. But I found out, that if you execute the test case manually in testlink (just create a build, click "test executing" and mark each test case in your test plan as "ok"), the testlink plugin gets all the test cases from the plan with the next run of the jenkins job.

          A B added a comment -

          Thanx. It works.

          However, the issue is not resolved - it is just a workaround.

          A B added a comment - Thanx. It works. However, the issue is not resolved - it is just a workaround.

          Thanks for the feedback @A B. A new version will get rolled out as soon as I get time to start a new dev cycle to work in the plug-in again.

          Bruno P. Kinoshita added a comment - Thanks for the feedback @A B. A new version will get rolled out as soon as I get time to start a new dev cycle to work in the plug-in again.

          @Sascha, it makes sense I think. The issue is happening because the plug-in added an option to filter by execution status (which was changed in the latest releases of the TestLink XML-RPC). I'll remove this feature and cut a new release. The alpha version was an experiment where I removed this feature from the core code, but not from the UI and other classes. Thanks!

          Bruno P. Kinoshita added a comment - @Sascha, it makes sense I think. The issue is happening because the plug-in added an option to filter by execution status (which was changed in the latest releases of the TestLink XML-RPC). I'll remove this feature and cut a new release. The alpha version was an experiment where I removed this feature from the core code, but not from the UI and other classes. Thanks!

          Code changed in jenkins
          User: Bruno P. Kinoshita
          Path:
          src/main/java/hudson/plugins/testlink/AbstractTestLinkBuilder.java
          src/main/java/hudson/plugins/testlink/GraphHelper.java
          src/main/java/hudson/plugins/testlink/TestLinkBuildAction.java
          src/main/java/hudson/plugins/testlink/TestLinkBuilder.java
          src/main/java/hudson/plugins/testlink/TestLinkBuilderDescriptor.java
          src/main/java/hudson/plugins/testlink/TestLinkInstallation.java
          src/main/java/hudson/plugins/testlink/TestLinkProjectAction.java
          src/main/java/hudson/plugins/testlink/TestLinkResult.java
          src/main/java/hudson/plugins/testlink/TestLinkSite.java
          src/main/java/hudson/plugins/testlink/util/TestLinkHelper.java
          src/main/resources/hudson/plugins/testlink/TestLinkBuilder/config.jelly
          src/test/java/hudson/plugins/testlink/TestTestLinkBuilder.java
          src/test/java/hudson/plugins/testlink/TestTestLinkSite.java
          http://jenkins-ci.org/commit/testlink-plugin/1f80f15ffcead970500f31f2333af09bef6af43b
          Log:
          [FIXED JENKINS-20339] reverting pull request 5, which enables Jenkins to filter by execution status

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/testlink/AbstractTestLinkBuilder.java src/main/java/hudson/plugins/testlink/GraphHelper.java src/main/java/hudson/plugins/testlink/TestLinkBuildAction.java src/main/java/hudson/plugins/testlink/TestLinkBuilder.java src/main/java/hudson/plugins/testlink/TestLinkBuilderDescriptor.java src/main/java/hudson/plugins/testlink/TestLinkInstallation.java src/main/java/hudson/plugins/testlink/TestLinkProjectAction.java src/main/java/hudson/plugins/testlink/TestLinkResult.java src/main/java/hudson/plugins/testlink/TestLinkSite.java src/main/java/hudson/plugins/testlink/util/TestLinkHelper.java src/main/resources/hudson/plugins/testlink/TestLinkBuilder/config.jelly src/test/java/hudson/plugins/testlink/TestTestLinkBuilder.java src/test/java/hudson/plugins/testlink/TestTestLinkSite.java http://jenkins-ci.org/commit/testlink-plugin/1f80f15ffcead970500f31f2333af09bef6af43b Log: [FIXED JENKINS-20339] reverting pull request 5, which enables Jenkins to filter by execution status

          3.8 released!

          Bruno P. Kinoshita added a comment - 3.8 released!

            kinow Bruno P. Kinoshita
            ab_ing A B
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: