Activate ReadyAPI on Headless Machines and in CI/CD build runs

The computer where you are going to run tests must have access to the SmartBear License Servers. The proxies and firewalls running in our 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.

Please note, as outlined here and in our Terms of Use: Floating licenses are required for scenarios including multiple authorized users, service accounts, and machine combinations including virtual machines and containerized environments. Floating licenses are required for any headless use case with virtual machines and docker.

It is a more secure way to specify the SmartBear account for the run by using an access key generated for your account.

1. Get the access key

You get the key in the SmartBear Licensing Portal:

For complete information, see Get Access Key in the Licensing Portal documentation.

2. Specify the access key in the command line

Activate with Access Key – Get the access key from the SmartBear Licensing Portal and use it as a command-line parameter, either as -accessKey or -K.

Sample Command:

testrunner.bat "c:\my tests\my-proj.xml" -accessKey "9a######-####-####-####-##########97"

Make sure to enclose the access key in quotes.
Note: The test engine doesn’t cache the access key on your computer. You need to specify it for every run.