Forum Discussion
I've found a working workaround, by using the previous older TestAdapter version 1.15069.139, till the fix will be available.
I share it with you since this could temporarily resolve the issue also for you and let it possible to not block your test automation execution.
You can specify it as follows within your release pipeline, writing the complete working version on the task after InstallTestCompleteAdapter:
- task: InstallTestCompleteAdapter@1.15069.139
displayName: "TestComplete test adapter installer"
continueOnError: false
inputs:
installExecutor: false
updateExecutor: false
With this configuration, next VSTest tasks will work as expected.
Surely, when SmartBear or Microsoft will provide the fix, this workaround will need to be reverted to get the latest TestAdapter version.
simonaferrara
Hi,
And thank you for reminding about this solution. It did not work a year or so ago when we had the same problem with Test Adapter, but now it works (at least for us). Probably, Azure fixed something that did not work previously...
Cheers,
/Alex
==========