Forum Discussion

tvklovesu's avatar
tvklovesu
Frequent Contributor
9 months ago

testscripts from jenkins not running on testExecute

Hi,

I don't know where to start from. We recently updated the testExecute on the server and from then when we run the jenkins pipeline build, they are not reaching the testexecute and not running. We don't see any sessions on selenium grid running. But when we run the same test script from our local machine connecting to remote server those scripts are running fine. We tried to restart the server, selenium grid and the testExecute agent, but no luck. The person who initially configured was left and now we are facing this issue. 

 

For some builds this is the last message in the console

[TestComplete] A TestComplete build step is already running on the node. Pausing the run until this built step is over...

 

And for some builds this is the last message

[TestComplete] Launching the test runner.
$ '"C:\Program Files (x86)\SmartBear\TestExecute 15\x64\bin\SessionCreator.exe"' ExecuteProcess '/c:""C:\Program Files (x86)\SmartBear\TestExecute 15\x64\bin\TestExecute.exe""
 "c:\var\lib\jenkins\workspace\Prod-Automation\Dartts-prod-smoke-pipeline\Prod_SmokeTest.pjs" /run /SilentMode /ForceConversion /ns /exit 
"/ExportLog:c:\var\lib\jenkins\workspace\Prod-Automation\Dartts-prod-smoke-pipeline\1692131710677.tclogx" 
"/ExportLog:c:\var\lib\jenkins\workspace\Prod-Automation\Dartts-prod-smoke-pipeline\1692131710677.htmlx" "/ErrorLog:c:\var\lib\jenkins\workspace\Prod-Automation\Dartts-prod-smoke-pipeline\1692131710677.txt"
 "/project:DARTTS_Prod_Smoke" /DoNotShowLog "/run" "/SilentMode" "/psv:env=prod" "/psv:ADFSusername=****" "/psv:ADFSpassword=****" /JenkinsTCPluginVersion:2.8.1'

 

jobs queue in jenkins

Selenium grid sessions

 

 Not sure what are we missing here. Do we need to do anything else when we update the testExecute agent. 

Integrations

23 Replies

Sort By
    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      I saw those posts, but my issue is different where it shows as running and no error message in the console. But not showing the activity in the selenium grid node. When you say plugin, do you mean jenkins plugin for testcomplete. We already have it right and the version is JenkinsTCPluginVersion:2.8.1. Should we need to update it?

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    9 months ago

    Was it working before you did "We recently updated the testExecute on the server" ?

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      yes, it's working fine. But as soon as we updated it started the issue.

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      So even if I upgrade the plugin, do you think it will not work?

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    9 months ago

    There's no harm in trying, providing you can revert back!

     

    Also, ensure there's no instances of TestExecute running on your remote machine.

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      I am trying to find what version of jenkins that will support TestComplete plugin version 2.9.1. Because our jenkins current version is 2.289.1.2, but the latest plugin version 2.9.2 supports Jenkins 2.361.4

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      Does TestExecute 15.54 supports TestComplete plugin 2.8.1. The previous version we were using was TE 15.40 and upgraded to 15.54 and now the issue started.

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    9 months ago

    I'm not sure. 

     

    Are you able to revert back to TE 15.40?

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      Hi,

      We have rollbacked the version for TestExecute on our VM, but still having same issue. It's not running the tests. I feel like there should be some connection between Jenkins and VM to run on Selenium grid and that part seems to be missing. Do I need to provide any selenium IP address on TestExecute?

      In our code when launching the browser, we have the following capabilities.

       

       

      var server = "http://w1idvrvnqas101.xxx.com:4444/"; //This is our selenium node server
/**/ var capabilities = {
"browserName": "chrome",
"goog:chromeOptions": {
"args": [
"--headless",
"screenResolution=1920x1080",
"--window-size=1920,1080",
"--page-size=90",
"--disable-gpu",
"--disable-dev-shm-usage",
"--no-sandbox",
]
}
}

       

      Do we need to provide selenium address in the TestExecute Options>Integration also even though we are providing it from our script

       

       

      • tvklovesu's avatar
        tvklovesu
        Frequent Contributor
        9 months ago

        Any thoughts on my previous post would be greatly appreciated as we are stuck in the middle of the cloud.

        Thanks

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      9 months ago

      no not yet. Before doing that we are trying to rule out all the possible scenarios. And for installing TestComplete in our local machine we are using On-premises license with an IP address. Can we use same IP address for TestExecute for licensed version?

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    9 months ago

    It's possible to use floating licenses. License is not just based on IP address, but I think machine hardware too.

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    8 months ago

    Are using SessionCreator?

     

    Are you using similar parameters for SessionCreator like this?

    'C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\SessionCreator.exe' RunTest /UserName:UserX /password:PasswordX /UseActiveSession /ScreenResolution:"1920*1080" /ProjectPath:"C:\Sandbox\TestComplete\ALS\ALS.pjs" /ExportLog:"C:\Sandbox\Log\index.html" /ExportSummary:"C:\Sandbox\Log\summary.html"

     

    Is your VM always unlocked? Do you use tscon?

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      8 months ago

      Our sessionCreator parameters is same as you shown. I have even provided that in my initial post.

      We are using VM and it's not unlocked always. We are not using tscon.

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    8 months ago

    The SessionCreator you had posted, is coming from Test Runner?

     

    Are you able to create a batch file with SessionCreator commands similar to what I have posted, and then get Test Runner to launch that batch file? Note, the machine needs to be unlocked - as mentioned in Running Tests via Remote Desktop

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      8 months ago

      This is the settings I see for Remote desktop connections in the slave machine

      And when we looked in the logs we see an error "SetAllAppPackagesPermissionsForProductDirectory: RegOpenKeyEx(HKEY_LOCAL_MACHINE\SOFTWARE\SmartBear\TestComplete\15.0\Setup) failed with error = 0x00000002."

      log trace

      
2023-08-31 15:31:23.711  6748   The beginning of the trace file.
2023-08-31 15:31:23.711  6748   Process information:
2023-08-31 15:31:23.712  6748       Name:     TestCompleteService15_2924
2023-08-31 15:31:23.712  6748       PID:      2924
2023-08-31 15:31:23.712  6748       Priority: 32
2023-08-31 15:31:23.712  6748       Session:  0
2023-08-31 15:31:23.712  6748       Host:     W1IPRRAVJEN001
2023-08-31 15:31:23.712  6748       CmdLine:  "C:\Program Files (x86)\SmartBear\TestExecute 15\Bin\TestCompleteService15.exe"
2023-08-31 15:31:23.712  6748       OS:       6.2.9200.2 
2023-08-31 15:31:23.713  6748   Module information:
2023-08-31 15:31:23.713  6748       Path:     C:\Program Files (x86)\SmartBear\TestExecute 15\Bin\TestCompleteService15.exe
2023-08-31 15:31:23.771  6748   ctor CTestCompleteServiceModule
2023-08-31 15:31:23.776  6748   TestCompleteService v15.40.0421.0
2023-08-31 15:31:23.776  6748   HKCR\AppID\{25575D8C-C512-427E-977F-D6F20C7EE4F2}
2023-08-31 15:31:23.777  6748      = 'TestCompleteService15'
2023-08-31 15:31:23.777  6748     LocalService = 'TestComplete 15 Service'
2023-08-31 15:31:23.777  6748   HKLM\SOFTWARE\SmartBear\TestCompleteService\15.0
2023-08-31 15:31:23.777  6748     C:\Program Files (x86)\SmartBear\TestExecuteLite 15\bin\TestCompleteService15.exe = ''
2023-08-31 15:31:23.777  6748     C:\Program Files (x86)\SmartBear\TestExecute 15\Bin\TestCompleteService15.exe = ''
2023-08-31 15:31:23.777  6748     NetworkSuitePort = DWORD:0x000017d9 (6105)
2023-08-31 15:31:23.783  6748   Dumps folder: C:\Windows\system32\config\systemprofile\AppData\Local\SmartBear\TestComplete\15.0\Logs\
2023-08-31 15:31:25.189  6748   Service::Start
2023-08-31 15:31:25.190  4724   SetAllAppPackagesPermissionsForProductDirectory: RegOpenKeyEx(HKEY_LOCAL_MACHINE\SOFTWARE\SmartBear\TestComplete\15.0\Setup) failed with error = 0x00000002.
2023-08-31 15:31:25.194  4724   SetAllAppPackagesPermissionsForProductDirectory: Calling SetNamedSecurityInfo(C:\Program Files (x86)\SmartBear\TestExecute 15\)
2023-08-31 15:31:25.195  9752   CTestCompleteServiceModule::PreMessageLoop
2023-08-31 15:31:25.209  9752   start Service::OnStart
2023-08-31 15:31:25.536  9752   end Service::OnStart
2023-08-31 15:31:34.384  4724   SetAllAppPackagesPermissionsForProductDirectory: SetNamedSecurityInfo(C:\Program Files (x86)\SmartBear\TestExecute 15\) returned
2023-08-31 15:31:34.385  4724   SetAllAppPackagesPermissionsForProductDirectory: succeeded.

       

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    8 months ago

    I've downloaded Jenkins v2.414.1 and have been playing about with it. I've setup three tests in TC which just displays messages. This is configured in Jenkins as no source control; project suite file C:\Sandbox\TCSamples\TestProjectX.pjs; running entire suite, actions on error: marked as failed and generate MHT log file. 

     

    When I run this, I get the following output

    and TC results shows,

    The agent is running on a VM, whilst there's an active user session

     

     

    • tvklovesu's avatar
      tvklovesu
      Frequent Contributor
      8 months ago

      Hi,

      Here is some more information on the issue. The system we are using is a EC2 VM with windows. Using cloudbees agent service controller and Test Execute 15.40 on the machine. The cloudbees agent service have the credentials for login and from Jenkins we don't need to provide any credentials to login to the VM. All we provide is the machine label. And in TestComplete service 15 we have selected "use local user session". Here in this service should we use same credentials similar to cloudbees or use local user session should be good.

      Sorry for not providing any screenshots as I don't have access to the VM. For everything we need to ask our admins to perform.

      Please let me know if any other information is needed.