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

Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • hp-application-automation-tools-plugin

      I'm having a reporting issue with the Jenkins plug-in for QC. I opened a bug in the Jira for their plug-in but no one has looked at it. Can you assist and discuss with Micro Focus if needed? I downgraded to 5.6.2 from 5.7 because of another issue "length cannot be zero". I've attached the build log that has the error. I have a test case in a test set 9 times. The point is that I need to run the test on 9 PCs. The error in the build log shows the 9th PC repeatedly and it should show 1,2,3,4..9. See attached files.

      To clarify, the Jenkins job is running three Test Sets. Each Test Set has one test to run on 9 PCs. The build log should show 27 test instances consisting of 3 (1-9) tests. The report should have 3 test instances of (1), (2), (3), .... (9). Instead, there are 27 instances of (9).

        1. build.log
          31 kB
        2. BuildStep.png
          BuildStep.png
          14 kB
        3. image-2019-09-17-10-11-01-078.png
          image-2019-09-17-10-11-01-078.png
          11 kB
        4. RunResults.png
          RunResults.png
          33 kB
        5. RunTestOnHostName.pptx
          195 kB
        6. Tests about to run.png
          Tests about to run.png
          20 kB

          [JENKINS-56750] Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

          Jim Sears added a comment - - edited

          aslaakso

          The older HP Plugin has an issue and if you built on top of that then I may not be able to use it. We are using the 5.62 because of that error so when I try your patch, I get this error.

          We are using HP QC 12.55.548 Patch 3.

           
          Started by user
          Jim Sears
          Building on master in workspace d:\Jenkins\.jenkins\workspace\MF QC Test Set Execution\Automation CoE\TAF LAB PC Maintenance-Files
          ERROR: Build step failed with exception
          java.lang.NullPointerException
          at com.microfocus.application.automation.tools.model.RunFromAlmModel.CreateProperties(RunFromAlmModel.java:161)
          at com.microfocus.application.automation.tools.model.RunFromAlmModel.getProperties(RunFromAlmModel.java:151)
          at com.microfocus.application.automation.tools.run.RunFromAlmBuilder.perform(RunFromAlmBuilder.java:211)
          at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
          at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
          at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
          at hudson.model.Build$BuildExecution.build(Build.java:206)
          at hudson.model.Build$BuildExecution.doRun(Build.java:163)
          at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
          at hudson.model.Run.execute(Run.java:1816)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:97)
          at hudson.model.Executor.run(Executor.java:429)
          Build step 'Execute Micro Focus functional tests from Micro Focus ALM' marked build as failure
          [WS-CLEANUP] Deleting project workspace...
          [WS-CLEANUP] Deferred wipeout is used...
          [WS-CLEANUP] done
          Finished: FAILURE

          Jim Sears added a comment - - edited aslaakso The older HP Plugin has an issue and if you built on top of that then I may not be able to use it. We are using the 5.62 because of that error so when I try your patch, I get this error. We are using HP QC 12.55.548 Patch 3.   Started by user Jim Sears Building on master in workspace d:\Jenkins\.jenkins\workspace\MF QC Test Set Execution\Automation CoE\TAF LAB PC Maintenance-Files ERROR: Build step failed with exception java.lang.NullPointerException at com.microfocus.application.automation.tools.model.RunFromAlmModel.CreateProperties(RunFromAlmModel.java:161) at com.microfocus.application.automation.tools.model.RunFromAlmModel.getProperties(RunFromAlmModel.java:151) at com.microfocus.application.automation.tools.run.RunFromAlmBuilder.perform(RunFromAlmBuilder.java:211) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute Micro Focus functional tests from Micro Focus ALM' marked build as failure [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] done Finished: FAILURE

          Jim Sears added a comment - - edited

          aslaakso

          For reference, I'm reinstalling 5.8 version to see if the error is different. I may need a second ticket for 5.8 :-0.

           

          5.8 has an issue and doesn't start the test run. Please see the log below.

           

          [RouteOne Medium] $ "d:\Jenkins\.jenkins\workspace\Agile Enablement Factories\Sales And Product\1-2 Dealer Sales\RouteOne Medium\HpToolsLauncher.exe" -paramfile props13092019181324010.txt
          "Started..."
          Timeout is set to: 7200
          Run mode is set to: RUN_PLANNED_HOST
          ============================================================================
          Starting test set execution
          Test set name: Demo, Test set id: 1423
          Number of tests in set: 5
          Test 1: [1]R1_AKL_CAL_BUS_LSE will run on host: <missing in log but is assigned in QC>
          Test 2: [1]R1_AKL_CAL_BUS_RET will run on host:
          Test 3: [1]R1_AKL_CAL_IND_LSE will run on host:
          Test 4: [1]R1_AKL_CAL_IND_RET will run on host:
          Test 5: [1]R1_AKL_CA_BUS_ERR will run on host:
          Problem while running TestSet: Exception from HRESULT: 0x80040459
          "Scheduler started at:13/09/2019 18:13:28
          -------------------------------------------------------------------------------------------------------
          Test set: Demo, finished at 13/09/2019 18:13:29
          ================================================
          Run status: Job succeeded, total tests: 5, succeeded: 0, failures: 0, errors: 0, warnings: 0
          Unknown:
          Unknown:
          Unknown:
          Unknown:
          Unknown:
          ================================================

           

          Jim Sears added a comment - - edited aslaakso For reference, I'm reinstalling 5.8 version to see if the error is different. I may need a second ticket for 5.8 :-0.   5.8 has an issue and doesn't start the test run. Please see the log below.   [RouteOne Medium] $ "d:\Jenkins\.jenkins\workspace\Agile Enablement Factories\Sales And Product\1-2 Dealer Sales\RouteOne Medium\HpToolsLauncher.exe" -paramfile props13092019181324010.txt "Started..." Timeout is set to: 7200 Run mode is set to: RUN_PLANNED_HOST ============================================================================ Starting test set execution Test set name: Demo, Test set id: 1423 Number of tests in set: 5 Test 1: [1] R1_AKL_CAL_BUS_LSE will run on host: <missing in log but is assigned in QC> Test 2: [1] R1_AKL_CAL_BUS_RET will run on host: Test 3: [1] R1_AKL_CAL_IND_LSE will run on host: Test 4: [1] R1_AKL_CAL_IND_RET will run on host: Test 5: [1] R1_AKL_CA_BUS_ERR will run on host: Problem while running TestSet: Exception from HRESULT: 0x80040459 "Scheduler started at:13/09/2019 18:13:28 ------------------------------------------------------------------------------------------------------- Test set: Demo, finished at 13/09/2019 18:13:29 ================================================ Run status: Job succeeded, total tests: 5, succeeded: 0, failures: 0, errors: 0, warnings: 0 Unknown: Unknown: Unknown: Unknown: Unknown: ================================================  

          Daniel Gront added a comment - - edited

          Hey jimsears, the other issue seems more severe. Please open another ticket so we can asses this properly.

          narcisamgalan FYI.

          Daniel Gront added a comment - - edited Hey jimsears , the other issue seems more severe. Please open another ticket so we can asses this properly. narcisamgalan FYI.

          Jim Sears added a comment -

          I opened the second ticket and tried the new beta patch and I feel like the new patch is working without errors but I am still experiencing the HostName problem. I am unable to run a test on a specific HostName. I've update the other ticket with the details and I think one of these is now a duplicate of the other.

          Let me know how you would like to proceed or if both tickets should remain open.
          Jim

          Jim Sears added a comment - I opened the second ticket and tried the new beta patch and I feel like the new patch is working without errors but I am still experiencing the HostName problem. I am unable to run a test on a specific HostName. I've update the other ticket with the details and I think one of these is now a duplicate of the other. Let me know how you would like to proceed or if both tickets should remain open. Jim

          Anda Sorina Laakso added a comment -

          Hi Jim,

          Since the patch solved the initial issue for this ticket, you should close this ticket and update the other ticket with all the details about the other issue.

          Thanks.

          Anda Sorina Laakso added a comment - Hi Jim, Since the patch solved the initial issue for this ticket, you should close this ticket and update the other ticket with all the details about the other issue. Thanks.

          Anda Sorina Laakso added a comment -

          Can you also provide me the properties file? Thanks.

          Anda Sorina Laakso added a comment - Can you also provide me the properties file? Thanks.

          Anda Sorina Laakso added a comment -

          As you can see on the attach image for me the host name is not missing, Did you remember to add itin the "advanced" section?

          Anda Sorina Laakso added a comment - As you can see on the attach image for me the host name is not missing, Did you remember to add itin the "advanced" section?

          Anda Sorina Laakso added a comment -

          As you can see in the attached image for the me the host name is present when selecting run on planed host option. Did you specify the host name in the "Advanced " section of the job configuration?

          Thanks.

          Anda Sorina Laakso added a comment - As you can see in the attached image for the me the host name is present when selecting run on planed host option. Did you specify the host name in the "Advanced " section of the job configuration? Thanks.

          Jim Sears added a comment -

          Hi aslaakso

          Before I close this ticket, may I ask two things from you?

          1) Repeat your exercise but add the same test "GUITest100" so that you have three instances, [1], [2], [3]. And set the "Another Host" to be Host1, Host2, Host3.

          When you look at the results, the test report should say what test ran on which PC. Your example is reversed because you use the same host.

          2) You asked if I populated the HostName but if I did, that would be inefficient. One Jenkins job runs 10 tests, each test on a different PC. If I set the HostName in the Jenkins job then I would have to set it to one PC. That means I would need 10 jobs, 1 for each PC to run one test.

          Please see attached PPT.

           

          Jim Sears added a comment - Hi aslaakso Before I close this ticket, may I ask two things from you? 1) Repeat your exercise but add the same test "GUITest100" so that you have three instances,  [1] ,  [2] ,  [3] . And set the "Another Host" to be Host1, Host2, Host3. When you look at the results, the test report should say what test ran on which PC. Your example is reversed because you use the same host. 2) You asked if I populated the HostName but if I did, that would be inefficient. One Jenkins job runs 10 tests, each test on a different PC. If I set the HostName in the Jenkins job then I would have to set it to one PC. That means I would need 10 jobs, 1 for each PC to run one test. Please see attached PPT.  

          Hilda added a comment - - edited

          Hello,

          I have tried to reproduce this issue, but it is working as expected for me with the latest plugin version.

          Are you facing the issue with the latest version of our plugin?

          I am going to Close this case, but feel free to reopen it anytime, and we can discuss further steps.

          Thank you,

          Hilda Both

          Hilda added a comment - - edited Hello, I have tried to reproduce this issue, but it is working as expected for me with the latest plugin version. Are you facing the issue with the latest version of our plugin? I am going to Close this case, but feel free to reopen it anytime, and we can discuss further steps. Thank you, Hilda Both

            aslaakso Anda Sorina Laakso
            jimsears Jim Sears
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: