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

Error when executing UFT test with the Micro Focus plugin

XMLWordPrintable

      After upgrading to the new "Micro Focus Application Automation Tools" plugin (v.5.5), from the version 5.4, I have experienced errors in the executions and the jobs are no longer working.

       

      The error shown is:

       

      Test: [1]XXXXX, Status: Error, Message: Unified Functional Testing error: Unable to connect the testing tool to the requested ALM/QC server.
      Error from Unified Functional Testing: Failure in Spider Module Process. Error: This type of installation requires that UAC be disabled. Disable UAC or run the program with administrator privileges \nLink: td://YYYYYY:8080/qcbin/TestLabModule-000000003649890581?EntityType=IRun&EntityID=6948\n

       

      Previously, the jobs were working fine with this configuration:

      Micro Focus Application Automation Tools v.5.4
      JIRA: 2.138.1
      ALM: 12.20
      UFT: 14.50

          [JENKINS-53583] Error when executing UFT test with the Micro Focus plugin

          Pere Felices added a comment - - edited

          The job that is showing the error is configured just with 2 steps:

          Build section: "Execute functional tests from Micro Focus ALM" (with a proper user and a proper path to the Test Set)

          Post-build Actions: "Publish Micro Focus test Result" (Always archive test reports)

          This job was working fine in the agents with the previous version of the plugin.

          I have tried executing the script manually from the agent (opening ALM and executing the script from there), and works fine. So, it seems that the error is with the plugin.

          Pere Felices added a comment - - edited The job that is showing the error is configured just with 2 steps: Build section: "Execute functional tests from Micro Focus ALM" (with a proper user and a proper path to the Test Set) Post-build Actions: "Publish Micro Focus test Result" (Always archive test reports) This job was working fine in the agents with the previous version of the plugin. I have tried executing the script manually from the agent (opening ALM and executing the script from there), and works fine. So, it seems that the error is with the plugin.

            akevinlee Kevin Lee
            perefm Pere Felices
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: