Activate TestComplete in CI/CD build runs

Running TestComplete from a CI/CD build means you start it from the command line.

To specify the SmartBear account to be used for the run, you use an access key generated for the account in the SmartBear License Management.

The explanation below works for both Fixed User and Floating types of SmartBear ID-based licenses.

Currently, all the control over license use is performed by the SmartBear license servers available 24×7. The computer where you are running TestComplete must have permanent access to these servers. That is, the proxies and firewalls running in your network should allow connection to them:

• https://manage.smartbear.com:443
• https://api.slm.manage.smartbear.com:443
• https://login.slm.manage.smartbear.com:443
• https://server.manage.smartbear.com:443
• https://server.slm.manage.smartbear.com:443
• https://profile.id.smartbear.com:443
• https://profile-api.id.smartbear.com:443
• https://auth.id.smartbear.com:443

This access is needed both at the product start and during the product runtime. The addresses are for API servers and don’t have a user interface visible in browsers. When products call these hosts, they add some specific paths or URLs to the addresses.

Log in to the SmartBear License Management and select  > Acess Key from the top right:

If needed, you can regenerate the key any time. To do this, simply click Regenerate.

See also Get Access Key in the License Management documentation.

Specify the key by using the -accessKey command-line parameter:

Make sure to enclose the access key in quotes.

The test engine doesn’t cache the access key on your computer. You need to specify it for every run.