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

Testlink plugin : generated TAP result files are not used for updating Testlink.

      Hello

      I'm currently evaluating Jenkins <=> Testlink communications and use TAP format for results.
      My env. is the following :

      • Win XP Pro
      • Jenkins 1.488
      • Testlink 1.9.3
      • Testlink plugin 3.1.8

      For testing purpose, I've just set two dummy test cases in Testlink and result files are generated with a bat file (see attached Test001.bat).
      It seems that, test case are correctly retrieved from testlink, execution seems ok too.
      But, when time comes to analyse test results, TAP files seem to be correctly identified (see systemlog.txt) but results are not extracted and testlink is not updated.
      If I generate a wrong TAP format, Testlink plugin correctly detects it and issues exceptions.

      Any ideas ?

      (Attachment contains Jenkins job, build, etc.)

          [JENKINS-15810] Testlink plugin : generated TAP result files are not used for updating Testlink.

          Hi Stéphane,

          Thanks for providing logs, configuration, and all the input values so well organized. That really helps analysing this issue.

          Your job configuration does looks correct, so I guess there might be something in the TestLink configuration.

          Your test cases (Test Current Time, and Test Current Time2) must have the custom field "Test Case Name" configured as "TestCurrentTime", in order to your job work properly.

          What the plug-ins does in your job is 1) using the given pattern look for test results, 2) for each results try to match the TAP file name with your key custom field, and then 3) update the results in TestLink.

          Can you give a try, please?

          Thanks!

          Bruno P. Kinoshita added a comment - Hi Stéphane, Thanks for providing logs, configuration, and all the input values so well organized. That really helps analysing this issue. Your job configuration does looks correct, so I guess there might be something in the TestLink configuration. Your test cases (Test Current Time, and Test Current Time2) must have the custom field "Test Case Name" configured as "TestCurrentTime", in order to your job work properly. What the plug-ins does in your job is 1) using the given pattern look for test results, 2) for each results try to match the TAP file name with your key custom field, and then 3) update the results in TestLink. Can you give a try, please? Thanks!

          Hello Bruno,

          Your indications really helped solving this configuration problem.
          Actually, I misunderstood content of those Custom fiedls and usage made by TestLink plugin.

          I've provided 2 screen captures with both my Testlink and Jenkins configurations. I hope this may help others.

          Best regards
          Stéphane

          stéphane benteux added a comment - Hello Bruno, Your indications really helped solving this configuration problem. Actually, I misunderstood content of those Custom fiedls and usage made by TestLink plugin. I've provided 2 screen captures with both my Testlink and Jenkins configurations. I hope this may help others. Best regards Stéphane

          Hi Stéphane! Glad to hear that that helped.

          I'm recording screencasts, and have already prepared a sample Virtual Machine with the plugin + jenkins + testlink configured. Hopefully that, plus this issue and your screenshots, will be enough to make sure other users don't have the same issue.

          Thanks! -B

          Bruno P. Kinoshita added a comment - Hi Stéphane! Glad to hear that that helped. I'm recording screencasts, and have already prepared a sample Virtual Machine with the plugin + jenkins + testlink configured. Hopefully that, plus this issue and your screenshots, will be enough to make sure other users don't have the same issue. Thanks! -B

            kinow Bruno P. Kinoshita
            sbenteux stéphane benteux
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: