Forum Discussion

VinothNageswara's avatar
VinothNageswara
New Contributor
2 years ago

Azure CI/CD pipeline - TestComplete could not start because the license check has failed

Hi 
 
Here is my CI/CD pipeline. I get the following error when I execute the pipeline.
We have a key based license. Should I put the accesskey as below  or it is not required? If so , where do i find the accesskey as I don't have a smartbear account.
Is accesskey same as License key ?
We have license only for TestComplete not for TestExecute , So have used TestComplete.
If there are any other issues in the pipeline , please advise.
 
taskVisualStudioTestPlatformInstaller@1
        inputs:
          packageFeedSelector'nugetOrg'
          versionSelector'latestStable'
    
      - taskInstallTestCompleteAdapter@1
        inputs:
          installExecutortrue
          updateExecutortrue
          accessKey:  'xxxxxx'
          searchModeExecutionPlan
          logsLevel'0'
          preferredExecutor'TC'

 

      - taskVSTest@2
        inputs:
          testSelector'testAssemblies'
          testAssemblyVer2'**\*.pjs'
          searchFolder'$(System.DefaultWorkingDirectory)'
          vsTestVersion'toolsInstaller'
          testRunTitle'Automated tests'
 
 
Outcome
Unable to connect to TestComplete: User authentication error. Token does not exist.User authentication error. Token does not exist. TestComplete could not start because the license check has failed.

1 Reply

  • Here is where we would add the Token during a CLI execution: https://support.smartbear.com/testcomplete/docs/licensing/id-based/automated-builds.html

    Ex in Yaml form:

    pool:
    name: VM Agent Pool
    steps:
    - task: VisualStudioTestPlatformInstaller@1
    displayName: 'Visual Studio Test Platform Installer'

    - task: SmartBearSoftware.install-testcomplete-adapter-task.install-testcomplete-adapter-task.InstallTestCompleteAdapter@1
    displayName: 'TestComplete test adapter installer'
    inputs:
    preferredExecutor: TC
    installExecutor: false
    updateExecutor: false
    accessKey: 'Your Access Key'

    - task: VSTest@2
    displayName: 'VsTest - testAssemblies'
    inputs:
    testAssemblyVer2: '**\*Project Suite executed'
    vsTestVersion: toolsInstaller