Forum Discussion

Hal1988's avatar
Hal1988
Occasional Contributor
23 days ago
Solved

TestComplete Test Adapter

We are using this task 'InstallTestCompleteAdapter@1' in my pipeline. Version: 1.15078.28 Till 12/11, there was no issue. Nothing changed on our side, and starting from yesterday (13/11), the task e...
test run
  • Hal1988's avatar
    Hal1988
    19 days ago

    Thank you for the reply.

    That is indeed true, the support of the '??' operator is only available in Node.js 14 and above. And this operator is used in the sources of this task version, as I can see it in main.js

    ..\InstallTestCompleteAdapter_1089cd2b-159b-4050-93fb-125ca13743c6\1.15078.28\main.js:649

    const major = Number(raw.major ?? raw.CurrentMajorVersionNumber ?? rel[0] ?? 10);

    Yes, I've checked that our build agent has changed with some DevOps update (I think). Unfortunately, we actually have no control over these build agent changes.  And in my environment, I have 3 versions of Node installed now, and this task always runs with Node 10 for some unknown reason. The other Node versions are also added to the system environments. Maybe pipeline uses it as a default (that's something I need to check), and if there is a possibility to change it to a specific Node version (in my case Node14 or above). 

    For now, as it's blocking my test runs, therefore, I have replaced the task with the older version i.e., InstallTestCompleteAdapter@1.15069.139. 

    Not the best solution, but it works for now!

Hal1988's avatar
Hal1988
Occasional Contributor
19 days ago

Thank you for the reply.

That is indeed true, the support of the '??' operator is only available in Node.js 14 and above. And this operator is used in the sources of this task version, as I can see it in main.js

..\InstallTestCompleteAdapter_1089cd2b-159b-4050-93fb-125ca13743c6\1.15078.28\main.js:649

const major = Number(raw.major ?? raw.CurrentMajorVersionNumber ?? rel[0] ?? 10);

Yes, I've checked that our build agent has changed with some DevOps update (I think). Unfortunately, we actually have no control over these build agent changes.  And in my environment, I have 3 versions of Node installed now, and this task always runs with Node 10 for some unknown reason. The other Node versions are also added to the system environments. Maybe pipeline uses it as a default (that's something I need to check), and if there is a possibility to change it to a specific Node version (in my case Node14 or above). 

For now, as it's blocking my test runs, therefore, I have replaced the task with the older version i.e., InstallTestCompleteAdapter@1.15069.139. 

Not the best solution, but it works for now!