TestExecute Integration With Jenkins

[nisgupta]

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: FAILURE


Also attached the screenshot that I have set up on Jenkins. Let me know if You all need more information.

Thanks
Nishchal

[cunderw]

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]

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]

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]

Checklists on Jenkins configuration:

1. Make sure you have your project in the current job workspace like below.
2. Make sure you have installed TestComplete/TestExecute in the slave machine
3. Make sure Jenkins slave is connected to Jenkins Master
4. 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.

[nisgupta]

@cunderw

Your updates is giving me lot of information about the jenkins configuration. I have very less experience with Jenkins. Till now I am successful with running the testcomeplete tests on my machine from my local jenkins . 

As discussed our main objective is to run the TestComplete tests on TestExecute machines . Currently TestExecute machines do not have jenkins installed Now as per your post, I need to install the jenkins in those machines and then we can configure them ?

Thanks

NG

[cunderw]

Correct, you have to install the jenkins slave agen on the Test Execute machines and configure them. The preparing jenkins link includes all of the needed details for this to work. If you have any specific issues or problems let us know. 

[nisgupta]

@cunderw 

@shankar_r

Thank you for the updates very much. We are trying to connect the testexecute machines with the jenkins server. there are some issues coming relating to connectivity and our administrator are working to reslove the connectivity issues.  Once those connectivity issues get resolved then will update how it is working or may be we will have some other issues in running tescomplete tests. Will updates once the connectivity issue get resolved.

Thanks

NG

[nisgupta]

@cunderw

So Now I am launching the jenkins server from the testexecute machine . I have attached the screenshot. 

When I press the lauch button I get the following error 

Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main createEngine

INFO: Setting up agent: slave_pretty

Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main$CuiListener <init>

INFO: Jenkins agent is running in headless mode.

Sep 27, 2018 9:54:20 AM hudson.remoting.Engine startEngine

INFO: Using Remoting version: 3.23

Sep 27, 2018 9:54:20 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir

INFO: Using C:\Users\nisgupta\Documents\TestComplete\remoting as a remoting work directory

Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main$CuiListener status

INFO: Locating server among [http://microcar.ttu.edu:8080/]

Sep 27, 2018 9:54:20 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve

INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]

Sep 27, 2018 9:54:25 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible

WARNING: connect timed out

Sep 27, 2018 9:54:25 AM hudson.remoting.jnlp.Main$CuiListener error

SEVERE: http://microcar.ttu.edu:8080/ provided port:60540 is not reachable

java.io.IOException: http://microcar.ttu.edu:8080/ provided port:60540 is not reachable

            at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286)

            at hudson.remoting.Engine.innerRun(Engine.java:523)

            at hudson.remoting.Engine.run(Engine.java:474)

[cunderw]

The error is showing that your test execute machine cannot connect to the remote jenkins master whichs sounds like a network / filewall issue. You would probably have to work with your infrastructure team to determine why you are being blocked.