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

Unable to find Test Set using path

    XMLWordPrintable

Details

    Description

      Hi,

      Despite all our efforts, we simply don't have the hp application automation Tools plugin find the correct test set when using path.

      Each time, we get this "node not found" in the console log, and it executes the first test set it finds having the same name

      Our issue is we can have multiple test sets with the same name in different places.

      Here, the target test set is Root\VABF_TIR_2\VABF_Prediweb_RIFR : It exists in ALM at that exact place.

      Any idea ?

      Démarré par l'utilisateur admin
      Running as SYSTEM
      Building on master in workspace C:\Users\UMC9TA\.jenkins\workspace\test uft
      [test uft] $ "C:\Users\UMC9TA\.jenkins\workspace\test uft\HpToolsLauncher.exe" -paramfile props06052020111103292.txt
      "Started..."
      Timeout is set to: -1
      Run mode is set to: RUN_LOCAL
      Unable to retrieve test set folder: Node not found.
      ============================================================================
      Starting test set execution
      Test set name: VABF_Prediweb_RIFR, Test set id: 2
      Test 1: [1]PDW-002a- Prediweb - Versement Libre (1) will run on host: CAAL41827
      Test 2: [1]PDW-001a- Prediweb - Adh‚sion (1) will run on host: CAAL41827
      Test 3: [1]PDW-001b- Prediweb - Adh‚sion (2) will run on host: CAAL41827
      Test 4: [2]PDW-001a- Prediweb - Adh‚sion (1) will run on host: CAAL41827
      Test 5: [2]PDW-001b- Prediweb - Adh‚sion (2) will run on host: CAAL41827
      log4net:ERROR [RollingFileAppender] Unable to acquire lock on file C:\Users\UMC9TA\.jenkins\workspace\test uft\. Impossible de trouver une partie du chemin d'accŠs 'C:\Users\UMC9TA\.jenkins\workspace\test uft\'.
      "Scheduler started at:06/05/2020 11:11:06
      -------------------------------------------------------------------------------------------------------
      06/05/2020 11:11:07 Running: [1]PDW-001a- Prediweb - Adh‚sion (1)

       

       

      Attachments

        Issue Links

          Activity

            redacted propfile content :

            #
            #Wed May 06 11:11:03 CEST 2020
            runType=Alm
            almRunHost=
            almApiKey=<redacted>
            almClientID=
            almTimeout=-1
            almDomain=DEFAULT
            FilterTests=false
            almProject=BAC_A_SABLE_JENKINS
            almPassword=<redacted>
            TestSet1=Root\\VABF_TIR_2
            VABF_Prediweb_RIFR
            almRunMode=RUN_LOCAL
            almUserName=UMC9TA
            almServerUrl=http\://vw-a-pxx-74/qcbin/
            SSOEnabled=false
            resultsFilename=Results06052020111103292.xml

            obo_fr Olivier BORDEREAU added a comment - redacted propfile content : # #Wed May 06 11:11:03 CEST 2020 runType=Alm almRunHost= almApiKey=<redacted> almClientID= almTimeout=-1 almDomain=DEFAULT FilterTests=false almProject=BAC_A_SABLE_JENKINS almPassword=<redacted> TestSet1=Root\\VABF_TIR_2 VABF_Prediweb_RIFR almRunMode=RUN_LOCAL almUserName=UMC9TA almServerUrl=http\://vw-a-pxx-74/qcbin/ SSOEnabled=false resultsFilename=Results06052020111103292.xml

            Micro Focus Application Automation Tools version 6.2

            obo_fr Olivier BORDEREAU added a comment - Micro Focus Application Automation Tools version 6.2
            obo_fr Olivier BORDEREAU added a comment - - edited

            the entry for TestSet1 copied here failed.
            In the file the testsetname is indicated correctly with double forward slashes
            TestSet1=Root\\VABF_TIR_2
            VABF_Prediweb_RIFR

            obo_fr Olivier BORDEREAU added a comment - - edited the entry for TestSet1 copied here failed. In the file the testsetname is indicated correctly with double forward slashes TestSet1=Root\\VABF_TIR_2 VABF_Prediweb_RIFR
            mihaicampean Mihai added a comment -

            Which ALM version are you using? 

            mihaicampean Mihai added a comment - Which ALM version are you using? 
            hildaboth Hilda added a comment - - edited

            If the paths are correctly specified MF Jenkins plugin using "Execute Micro Focus functional tests from Micro Focus ALM" as build step should be able to find all the test sets correctly.

            We have checked the issue on our side with the latest plugin version, and the issue is reproduced, using runFromAlmBuilder with pipeline.

            We are fixing the issue. 

            hildaboth Hilda added a comment - - edited If the paths are correctly specified MF Jenkins plugin using "Execute Micro Focus functional tests from Micro Focus ALM" as build step should be able to find all the test sets correctly. We have checked the issue on our side with the latest plugin version, and the issue is reproduced, using runFromAlmBuilder with pipeline. We are fixing the issue. 
            hildaboth Hilda added a comment -

            Hello,

            This issue for the Test Sets was fixed in the latest Jenkins plugin release 6.9. 

            Because of the "Unable to retrieve test set folder: Node not found." message we are going to Reopen the case, and will include the fix in the next release.

            Thank you.

            hildaboth Hilda added a comment - Hello, This issue for the Test Sets was fixed in the latest Jenkins plugin release 6.9.  Because of the "Unable to retrieve test set folder: Node not found." message we are going to Reopen the case, and will include the fix in the next release. Thank you.

            People

              dbogdan7 Dorin Bogdan
              obo_fr Olivier BORDEREAU
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: