We are looking for the ways - how Jenkins can run the projects located in TestExecute machines. Here is our case. At this now now Source code management and so no git. Jenkins is set up on my machine which is local to my machine. We have installed the TestExecute on 3 Virtual machines which have window OS. We have projects located on these machines. Now When Jenkins run those projects I got the following errors Started by user Nishchal Gupta Building remotely on pretty.ttu.edu in workspace C:\Jenkins\workspace\Scholarship [TestComplete] The test execution started (/\\pretty.ttu.edu\Users\nisgupta\Documents\TestComplete\IS\Student\FASBS\Financial Aid SBS\Scholarship Application\Scholarship Application.pj). [TestComplete] Found TestComplete/TestExecute installations: Type: TC, Version: 12.50.4142.7, Path: "C:\Program Files (x86)\SmartBear\TestComplete 12\bin\TestComplete.exe" [TestComplete] [ERROR] Unable to find the specified TestComplete/TestExecute installation. [TestComplete] Marking the build as FAILED. Build step 'TestComplete Test' changed build result to FAILURE Build step 'TestComplete Test' marked build as failure Finished: FAILUREAlso attached the screenshot that I have set up on Jenkins. Let me know if You all need more information.ThanksNishchal

Have you followed below steps to activate your slave? New Node --> Enter Node Name. Select Dumb Slave --> Press OK. Fill out the following: Set a number of executors (one or more) as needed. Set a Remote FS Root, a home directory for the master on the slave machine. For a Windows slave, use something like: "C:\Jenkins\" TODO: add details. Select the appropriate Usage setting: For an additional worker: Utilize this slave as much as possible For specialized jobs: Leave this machine for tied jobs only Launch Method: An easy way to control a Windows slave is by using Launch slave agents via Java Web Start (Recommended for Windows) TODO: add steps for other methods. Availability --> Keep this slave online as much as possible TODO: add details for each option. Press OK. Now you need to connect your slave machine to the master using the following steps. On you slave machine go to the Jenkins server url. Go to Manage Jenkins > Manage Nodes, Click on the newly created slave machine. Click on the Launch button to launch agent from browser on slave. Run the program. Now you should see the Slave machine connected under Nodes. If you want the service to run on start-up of the slave machine do the following (Windows only directions): In the Slave agent program running on your slave machine, click File --> Install as Windows Service. Start, type Services and Select the Services program. Find Jenkins Slave in the list, Double click to open. Select Startup type --> Automatic. Go to the Log On tab, change the Log on as to a user of your choice (Special user account Jenkins recommended). Make sure that auto login is set for the slave machine for the user account, then the VM (or physical computer) should connect and be available when needed.

Looks like the same proble someone else had: https://community.smartbear.com/t5/TestComplete-Desktop-Testing/TestComplete-Jenkins-Plugin-GUI-test-TestComplete-did-not-launch/td-p/148170/page/2 Solved by running jenkins as a local account.

It is not the Jenkins confluence publisher plugin limitation. The default rule for Jenkins is, each build step checks the previous step status if it is not SUCCESS then it won't go to next build/post build step and it stops where an error occurs. Some plug-ins might have override options so that irrespective of previous step status it will run. From Document: Action on warnings - Specifies whether Jenkins should mark the entire build as failed or unstable when the TestComplete test log contains warnings. Action on errors - Specifies whether Jenkins should mark the entire build as failed or unstable when the TestComplete test log contains errors. Answer to question is, Make the two drop-down boxes in the TestComplete build step advanced options to None as like below image then you are all set.

You're getting an out of memory error, which probably means your mht is way too big. I would look into Log.LockEvents(); to reduce the number of events being logged and images which is likely what's causing the huge file size.

It's not running because the machine you have setup as a Jenkins Slave does't have Test Execute installed, only Test Complete, and you have specified to run Test Execute: [TestComplete] Found TestComplete/TestExecute installations: Type: TC, Version: 12.50.4142.7, Path: "C:\Program Files (x86)\SmartBear\TestComplete 12\bin\TestComplete.exe" [TestComplete] [ERROR] Unable to find the specified TestComplete/TestExecute installation. The machines you want to run tests on must be configured as jenkins slave with the matching test runner installed. I also noticed in your screenshots that you don't have the projectuiste file or project configured properly. You have to specifify the path of the project sutie file relative your remote workspace, and then reference just the name of the project if you don't want to run the entire suite. More information on the requirements and how to properly set it up can be found here: https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/running-tests.html

TestExecute Integration With Jenkins

cunderw
Community Hero
7 years ago
It's not running because the machine you have setup as a Jenkins Slave does't have Test Execute installed, only Test Complete, and you have specified to run Test Execute:

[TestComplete] Found TestComplete/TestExecute installations: Type: TC, Version: 12.50.4142.7, Path: "C:\Program Files (x86)\SmartBear\TestComplete 12\bin\TestComplete.exe" [TestComplete] [ERROR] Unable to find the specified TestComplete/TestExecute installation.

The machines you want to run tests on must be configured as jenkins slave with the matching test runner installed.

I also noticed in your screenshots that you don't have the projectuiste file or project configured properly.

You have to specifify the path of the project sutie file relative your remote workspace, and then reference just the name of the project if you don't want to run the entire suite.

More information on the requirements and how to properly set it up can be found here:

https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/running-tests.html
- nisgupta
  Valued Contributor
  7 years ago
  Thank you for updates .
  
  Here are some things I need to Understand
  
  It's not running because the machine you have setup as a Jenkins Slave does't have Test Execute installed, only Test Complete, and you have specified to run Test Execute:
  
  This machine has TestComplete only which is used for development of scripts. We don't need to install TestExecute , right ?
  
  The machines you want to run tests on must be configured as jenkins slave with the matching test runner installed.
  
  All the TestExecute machines need to have jenkins installed ? What I have to do ?
  
  https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/running-tests.html
  
  The link is not working
  
  Thanks
  
  NG
  - cunderw
    Community Hero
    7 years ago
    Try these links, it does look like there might be some DNS issues with the smartbear site right now though you might have to copy and paste them into a new window / tab.
    
    https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/running-tests.html
    
    You have configured your machine with Test Complete that you use for development as the Jenkins Slave to run the tests. If this is not the machine you want running the tests then you need to configure the other machines, otherwise how is Jenkins going to know to connect to them?
    
    Any machine that is going to run the tests from jenkins has to be configured as a slave with the appropriate runner installed.
    
    I suggest following through the preparing steps here for any machines you want to run tests.
    
    https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/preparing.html
shankar_r
Community Hero
7 years ago
Checklists on Jenkins configuration:

Make sure you have your project in the current job workspace like below.

Make sure you have installed TestComplete/TestExecute in the slave machine

Make sure Jenkins slave is connected to Jenkins Master

Make sure you have licensed all machines

If you did all the above and still facing issue then put some more screenshots on the Jenkins configuration.

Forum Discussion

TestExecute Integration With Jenkins

Related Content

TestExecute + Jenkins

TestExecute 15.20 + Jenkins issue

TestComplete + Jenkins Integration

TestExecute fail on Jenkins

GitHub & Jenkins integration with TestComplete & TestExecute

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test