英文:
Azure DevOps Pipelines VsTest - The active test run was aborted. Reason: No suitable test runtime provider was found for any source in this run
问题
I've recently run into this issue while building pipelines that were previously working and were unchanged. All of the data logs of old pipeline runs show that the VsTest version used for testing was 2.219.0, while the ones failing are 2.220.0. Not sure if there is anything in the new version causing things to break. The VsTest section of the yaml file of the pipelines looks like this:
- task: VSTest@2
displayName: Run VSTests
inputs:
testSelector: 'testAssemblies'
testAssemblyVer2: |
**\*test*.dll
!**\*TestAdapter.dll
!**\obj\**
searchFolder: '$(System.DefaultWorkingDirectory)'
vsTestVersion: 'toolsInstaller'
testRunTitle: 'run unit tests'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
Has anyone ran into this lately?
I've tried changing vsTestVersion to 'latest', and it gets passed the error mentioned but it then fails to connect to a TestHost.
英文:
I've recently run into this issue while building pipelines that were previously working and were unchanged. All of the data logs of old pipeline runs show that the VsTest version used for testing was 2.219.0, while the ones failing are 2.220.0. Not sure if there is anything in the new version causing things to break. The VsTest section of the yaml file of the pipelines looks like this:
- task: VSTest@2
displayName: Run VSTests
inputs:
testSelector: 'testAssemblies'
testAssemblyVer2: |
**\*test*.dll
!**\*TestAdapter.dll
!**\obj\**
searchFolder: '$(System.DefaultWorkingDirectory)'
vsTestVersion: 'toolsInstaller'
testRunTitle: 'run unit tests'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'
Has anyone ran into this lately?
I've tried changing vsTestVersion to 'latest', and it gets passed the error mentioned but it then fails to connect to a TestHost
答案1
得分: 5
你可能遇到了 Visual Studio 测试版本 17.6 中的这个错误:https://github.com/microsoft/vstest/issues/4516
解决方法 1 对我有效。
英文:
You might be hitting this bug in VS test v 17.6: https://github.com/microsoft/vstest/issues/4516
Workaround 1 worked for me.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论