Forum Discussion
i am getting this also. would going back to the previous version of testexecute resolve it, at least, temporarily until it can be fixed?
- rwood_cert2 years agoOccasional Contributor
Bit of cross posting between threads, but managed to get a workaround with passing/working tests, did involve converting a Release pipeline to YAML, so we were able to use the prior TestComplete test adapter extension in Azure DevOps.
See my post here for details - https://community.smartbear.com/t5/TestComplete-Questions/Azure-Pipeline-Visual-Studio-Test-Test-execute-fails-to-run-but/m-p/254463/highlight/true#M110846
- dhundley2 years agoRegular Contributor
as I posted a few minutes ago, i'm still on the latest release of testexecute, my pipeline is still using the classic editor (not YAML) and my pipelines are running successfully without encountering the "cannot start process. . . ." error. the only thing i had to do was have testexecute running all the time.
Related Content
- 12 years ago
- 14 years ago
- 8 years ago
Recent Discussions
- 3 days ago