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

When creating a new build in TestLink, plugin should automatically assign test case execution to a user

      TestLink only reports some statistics correctly when executed test cases have been assigned to a user. Although it is possible to change the assignment manually post-execution it would be better if the TestLink plugin did this automatically when creating a new build e.g. assign all test cases (to be) executed by Jenkins to a jenkins-ci TestLink user.
      This may also require changes to the TestLink API.

          [JENKINS-13629] When creating a new build in TestLink, plugin should automatically assign test case execution to a user

          Hmm, good RFE. We may really need to change a few things in TestLink API, but that will be a great feature. Last week I was working on another project, but in May I will work on Jenkins and plug-ins again. Thanks for reporting, will try to work on this as soon as possible.

          Bruno P. Kinoshita added a comment - Hmm, good RFE. We may really need to change a few things in TestLink API, but that will be a great feature. Last week I was working on another project, but in May I will work on Jenkins and plug-ins again. Thanks for reporting, will try to work on this as soon as possible.

          Hi Robert, I will add the required code in TestLink XMl-RPC/TestLink Java API/Jenkins Plug-in, but first would like your feedback on some items:

          • We will assign the test to the user that jenkins is using (it is the user whom owns the devKey that Jenkins is configured to use)
          • Should we assign the test execution a) before test execution or b) after test execution (in case the build failed, and we chose a), the tests would have been assigned but not executed).
          • By default, we keep the same behaviour as now. There will be a new field for setting the assigned user name (later I will add a method to list the users, after thinking if it wouldn't be a security issue)

          Thanks!

          Bruno P. Kinoshita added a comment - Hi Robert, I will add the required code in TestLink XMl-RPC/TestLink Java API/Jenkins Plug-in, but first would like your feedback on some items: We will assign the test to the user that jenkins is using (it is the user whom owns the devKey that Jenkins is configured to use) Should we assign the test execution a) before test execution or b) after test execution (in case the build failed, and we chose a), the tests would have been assigned but not executed). By default, we keep the same behaviour as now. There will be a new field for setting the assigned user name (later I will add a method to list the users, after thinking if it wouldn't be a security issue) Thanks!

          Chris Nemes added a comment -

          Is it still planned to complete this issue. This would be very usefull as many of testlink reports do not show builds that are not assigned a user. Either way thanks for the work and effort put into the project.

          Chris Nemes added a comment - Is it still planned to complete this issue. This would be very usefull as many of testlink reports do not show builds that are not assigned a user. Either way thanks for the work and effort put into the project.

            kinow Bruno P. Kinoshita
            robertc Robert Campbell
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: