-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSTest@2 - Visual Studio 2022 not supported when explicit version is requested #16489
Comments
I wanted to downgrade VSTest in my pipeline to 17.2 or at least 17.0, because 17.3 introduced some serious code coverage issues with my code - probably due to the I worked around that by running the test suite in standalone VS Test Platform instead of stock Visual Studio present in the agent. I did that by changing - task: VisualStudioTestPlatformInstaller@1
inputs:
versionSelector: 'specificVersion'
testPlatformVersion: '17.2.0'
- task: VSTest@2
inputs:
vsTestVersion: 'toolsInstaller' Execution log may include a (false) warning that it doesn't include code coverage, but it's generated correctly. Read more here: #15449 |
Any updates? |
@max-zaytsev Gentle ping. Also as far as I see '17.0` is not mentioned in the documentation |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
For anyone visiting this issue: this might be resolved in #17858 based on the comments in a PR linked above. |
Required Information
Question, Bug, or Feature?
Type: Bug
Task Name: VSTest@2
Issue Description
The testing task is started using the following YAML:
The build server has Visual Studio 2022 installed and the VSBuild@2 task completes when
vsVersion: 17.0
is passed. When the VSTest task starts then it will stop with the error "Given test platform version 17.0 is not supported."It looks like people have been troubleshooting the root cause in the comments of issue 15522:
#15522 (comment)
Error logs
The text was updated successfully, but these errors were encountered: