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

Feedback and Improvement Suggestions for the HP QC Plugin

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: qc-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      Hi Romain and Thomas,

      thanks a lot for contributing your HP QC plugin, this is very much appreciated.
      I like to give some feedback from what I figured out so far:

      1. I have successfully tested your plugin with HP QC 10 and HP Functional Test 10, so you may add this version to the supported versions as well. No changes were necessary since the VBS you used is compatible with the QC 10 API. In fact it is also compatible with the QC 11 API, but I encountered some problems instantiating the scheduler object on HP ALM 11 PA, so I will retry once HP ALM 11 SP1 is out.

      2. While debugging an initial COM problem, it would have helped a lot if you would not use "On Error Resume Next" but "On Error Goto 10" in your VBS. Otherwise, error messages are not displayed but the script continues to wait for successful test set execution until it eventually times out.

      3. I was not able to get the plugin running if Hudson was installed as a Windows Service (even after I allowed the service to interact with the Desktop). Have you made similar experiences (and if yes, may you document this in the wiki).

      4. I could not figure out why you have to specify a path to QC/QTP in the Hudson setup. The VBS will find the DLLs on itself and I guess there are lots of Hudson administrators who do know their QC URL but do not know where the DLLs have been installed. Is it to ensure that all necessary DLLs are installed on the Hudson host? If so, could you add to the documentation that this step is not necessary if you can already run QTP tests from the QC GUI on the Hudson host?

      5. Would it be possible to have a script editor for the VBS built into Hudson? A plain text editor would be sufficient for me. My plan is to use Hudson's environment variables (like the current build number/revision number) to dynamically determine which test sets/tests to run. One would also need this setting if the test set scheduler should be instantiated on another host.

      6. Have you ever tried executing HP Performance Center (aka LoadRunner) tests contained in a QC test set?

      7. If Hudson is not running on the same box as QTP, one has to change the DCOM security settings on the QTP host. A link to HP's documentation how to do that ("Running Automation Scripts on a Remote Computer" in QTP Help) would be nice.

      Looking forward to your answers and always willing to help if needed.

      Best, Johannes Nicolai

      CollabNet

        Attachments

          Activity

          Hide
          rseguy Romain Seguy added a comment -

          Hi Nicolai (I hope I've not inverted first name/last name, tell me otherwise), thanks very much for your feedback.

          1. Thanks for the report. I guess the installer has changed anyway, so the plugin will need an update to support the installation of QC 10.

          2. May you provide a patch for this enhancement? I now have 7 Hudson plugins to maintain, so I have very little time to do the fixes myself (+ I nearly always apply patches that are provided to me).

          3. We run it with Hudson installed as a service. We had to do some special setup regarding the user so that he has access to the desktop, but I don't know exactly which ones since I don't have hands on infra.

          4. In fact we need these paths to automatically install QC and/or QTP in dedicated folders (if not specified, the plugin uses built-in paths). I'll try to clarify the doc on that point so that users don't worry about that if QC/QTP is already in the place.

          5. It's possible to do that. If you provide me with a patch it would be good (no time till the end of the year).

          6. Not yet. Maybe next year.

          7. OK, I'll update the Wiki page + some of the help messages regarding that.

          Thanks again for the feedback,
          Romain

          Show
          rseguy Romain Seguy added a comment - Hi Nicolai (I hope I've not inverted first name/last name, tell me otherwise), thanks very much for your feedback. 1. Thanks for the report. I guess the installer has changed anyway, so the plugin will need an update to support the installation of QC 10. 2. May you provide a patch for this enhancement? I now have 7 Hudson plugins to maintain, so I have very little time to do the fixes myself (+ I nearly always apply patches that are provided to me). 3. We run it with Hudson installed as a service. We had to do some special setup regarding the user so that he has access to the desktop, but I don't know exactly which ones since I don't have hands on infra. 4. In fact we need these paths to automatically install QC and/or QTP in dedicated folders (if not specified, the plugin uses built-in paths). I'll try to clarify the doc on that point so that users don't worry about that if QC/QTP is already in the place. 5. It's possible to do that. If you provide me with a patch it would be good (no time till the end of the year). 6. Not yet. Maybe next year. 7. OK, I'll update the Wiki page + some of the help messages regarding that. Thanks again for the feedback, Romain
          Hide
          jnicolai jnicolai added a comment -

          Added patch to detect situations where test set execution scheduler cannot be instantiated

          Show
          jnicolai jnicolai added a comment - Added patch to detect situations where test set execution scheduler cannot be instantiated
          Hide
          jnicolai jnicolai added a comment -

          Hi Romain,

          my first name actually is "Johannes" 8-)

          I attached a patch to detect if the test set execution scheduler could not be executed. After reviewing the source again I figured that On Error Goto 0 would not give us the chance to react with a reasonable error message, so explicit null checks in the code seemed to be a better approach.

          Best, Johannes

          Show
          jnicolai jnicolai added a comment - Hi Romain, my first name actually is "Johannes" 8-) I attached a patch to detect if the test set execution scheduler could not be executed. After reviewing the source again I figured that On Error Goto 0 would not give us the chance to react with a reasonable error message, so explicit null checks in the code seemed to be a better approach. Best, Johannes
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : rseguy
          Path:
          trunk/hudson/plugins/qc/src/main/resources/runTestSet.vbs
          http://jenkins-ci.org/commit/37036
          Log:
          [FIXED JENKINS-8098]

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : rseguy Path: trunk/hudson/plugins/qc/src/main/resources/runTestSet.vbs http://jenkins-ci.org/commit/37036 Log: [FIXED JENKINS-8098]
          Hide
          rseguy Romain Seguy added a comment -

          Thanks for the patch Johannes, I've applied it with as-is (adding your name + company in the MIT headers). Don't hesitate to submit other patches or even contributing directly to the Wiki page.

          MfG,
          Romain

          Show
          rseguy Romain Seguy added a comment - Thanks for the patch Johannes, I've applied it with as-is (adding your name + company in the MIT headers). Don't hesitate to submit other patches or even contributing directly to the Wiki page. MfG, Romain
          Hide
          craigc craig c added a comment -

          Hi Guys - Any updates on this?
          Thanks,
          Craig

          Show
          craigc craig c added a comment - Hi Guys - Any updates on this? Thanks, Craig
          Hide
          rseguy Romain Seguy added a comment -

          Closing the request; Was delivered in 1.1.

          Show
          rseguy Romain Seguy added a comment - Closing the request; Was delivered in 1.1.

            People

            • Assignee:
              rseguy Romain Seguy
              Reporter:
              jnicolai jnicolai
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: