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

Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System

    Details

    • Similar Issues:

      Description

      Our requirement is to kick off a UFT test on a slave agent. It works fine as long as that Slave agent is connected via RDP but if RDP is not there then UFT test on slave agent fails.

      So is it even possible to run a UFT test on a machine which is locked out or RDP connection is not there ? Has anyone done that before using any of the plugin?

        Attachments

          Activity

          Hide
          murali2018 Murali R added a comment -

          Hi All,

          We are also facing similar issue. Any solution to this issue ?

          Please let us know if we have any workaround or solution to this issue.

           

          Show
          murali2018 Murali R added a comment - Hi All, We are also facing similar issue. Any solution to this issue ? Please let us know if we have any workaround or solution to this issue.  
          Hide
          poppsalways Poojaa Sudhakaran added a comment -

          Hello Team,

          We are also trying to establish a similar setup. Could you please let us know if you've any solution for this issue?

           

          Show
          poppsalways Poojaa Sudhakaran added a comment - Hello Team, We are also trying to establish a similar setup. Could you please let us know if you've any solution for this issue?  
          Hide
          denisab85 Denis Abakumov added a comment - - edited

          I can confirm this for UFT 14.50 on Jenkins 2.190.3 with Micro Focus Application Automation Tools 5.9.

          No matter if the job is started by timer or manually, it will fail if an RDP session is disconnected.

          The output will be:

          Run build tests
          Launcher timeout is 10675199::02:48:05
          Controller Polling Interval: 30 seconds
          PerScenarioTimeout: 00::00:10:00 minutes
          FileSystemTestRunner timeout is 10675199.02:48:05.4775807
          UFT Mobile connection info is - UFT Mobile HostAddress: , Port: 8080, Username: , TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: 
          Results directory is: C:/Projects/UFT_Results
          1 tests found:
          C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02
          ============================================================================
          26-11-2019 07:37:14 Running: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02
          Test result: Error
          26-11-2019 07:37:14 Test complete: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02
          -------------------------------------------------------------------------------------------------------
          ================================================
          Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1, warnings: 0
          Error  : C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02
          ================================================
          Build step 'Execute Micro Focus tests from file system' changed build result to FAILURE
          Recording test results
          Report archiving mode is set to: ALWAYS_ARCHIVE_TEST_REPORT
          artifactsDir: archive C:\Program Files (x86)\Jenkins\jobs\UFT_Project\builds\58\archive
          Finished: FAILURE
          
          Show
          denisab85 Denis Abakumov added a comment - - edited I can confirm this for UFT 14.50 on Jenkins 2.190.3 with Micro Focus Application Automation Tools 5.9. No matter if the job is started by timer or manually, it will fail if an RDP session is disconnected. The output will be: Run build tests Launcher timeout is 10675199::02:48:05 Controller Polling Interval: 30 seconds PerScenarioTimeout: 00::00:10:00 minutes FileSystemTestRunner timeout is 10675199.02:48:05.4775807 UFT Mobile connection info is - UFT Mobile HostAddress: , Port: 8080, Username: , TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: Results directory is: C:/Projects/UFT_Results 1 tests found: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02 ============================================================================ 26-11-2019 07:37:14 Running: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02 Test result: Error 26-11-2019 07:37:14 Test complete: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02 ------------------------------------------------------------------------------------------------------- ================================================ Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1, warnings: 0 Error : C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02 ================================================ Build step 'Execute Micro Focus tests from file system' changed build result to FAILURE Recording test results Report archiving mode is set to: ALWAYS_ARCHIVE_TEST_REPORT artifactsDir: archive C:\Program Files (x86)\Jenkins\jobs\UFT_Project\builds\58\archive Finished: FAILURE
          Hide
          krisdinesh Dinesh Krishnaswamy added a comment -

          For all the followers, I dont think its gonna be fixed anytime sooner regardless of its criticality as it is lingering since 2017. If this is fixed you dont need micro focus CI solution

          I would suggest to move away from UFT is the only reliable solution. There are many great solutions are in place like Katalon Studio, Test Project which are awesome, supports the UI/API testing and also pretty much compatible with CI tools like Jenkins/Gitlab/github actions etc. Moreover all are completely free

          Please work on phased approach and it will be little tedious but you wont regret the effort that you put in to move away from UFT. 

          Happy weekend pals!!

          Show
          krisdinesh Dinesh Krishnaswamy added a comment - For all the followers, I dont think its gonna be fixed anytime sooner regardless of its criticality as it is lingering since 2017. If this is fixed you dont need micro focus CI solution I would suggest to move away from UFT is the only reliable solution. There are many great solutions are in place like Katalon Studio, Test Project which are awesome, supports the UI/API testing and also pretty much compatible with CI tools like Jenkins/Gitlab/github actions etc. Moreover all are completely free Please work on phased approach and it will be little tedious but you wont regret the effort that you put in to move away from UFT.  Happy weekend pals!!
          Hide
          genshaft Avi Genshaft added a comment -

          The issue was resolved more then a year ago, it requires UFT configurations. Please see our official documentation on how to configure it properly:

          https://admhelp.microfocus.com/uft/en/14.50-14.53/UFT_Help/Content/User_Guide/RunYourTest_DisconnectedRDP.htm?Highlight=locked%20session

          In addition on the slave machine identity of QuickTestProfessionalAutomation object should be set to "interactive user"

          Show
          genshaft Avi Genshaft added a comment - The issue was resolved more then a year ago, it requires UFT configurations. Please see our official documentation on how to configure it properly: https://admhelp.microfocus.com/uft/en/14.50-14.53/UFT_Help/Content/User_Guide/RunYourTest_DisconnectedRDP.htm?Highlight=locked%20session In addition on the slave machine identity of QuickTestProfessionalAutomation object should be set to "interactive user"

            People

            • Assignee:
              genshaft Avi Genshaft
              Reporter:
              praghav Pushpendra Raghav
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: