azure-pipelines-tasks: ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work.

Dear Microsoft, please fix this annoying bug

It’s really problematic, because my warning are filled with this line, and I don’t see the real warnings easily on my build reports.

@jakubch1 could you please update the assignee for this issue? it seems @phanikmmsft does not work on this project anymore?

Still a problem

This issue is still occurring. Bumping thread.

@abhadauria1 any update on removing this warning?

Still occurring with 17.5.0-preview

@phanikmmsft could you please simply remove this warning from your code? Code coverage is using now CLR Instrumentation Engine and Intellitrace files are not needed anymore so this warning is useless.

The latest VsTest Task version (>=2.235.0) is working as expected and should be available to consume where logging of unnecessary warnings isn’t happening. Hence, closing the issue. Please feel free to reopen the issue if it persists.

With VsTest task version 2.235.0, this issue should be resolved while consuming the latest test platform versions ( > 17.0.0).

Same issue here. All releases after 16.11 will result i a flood of warnings. Tryed out new xunit 2.5 and newest vstest runner.

I have the same issue in 17.6.3 , when that will be fixed???

I’m seeing this warning three times in my output. I have a single test task with a single test. It warns three times. This issue has been open for two years. Is it really possible that there’s no workaround and no fix for the latest version of the standard testing task?

Just for clarification. We set the Visual Studio test platform installer task to use v16.11.0 of the test tools and the issue went away

The changes were merged yesterday only. It would be gradually rolled out to all the Azure DevOps organization within next 15-20 days. No changes are required from your end. As and when the deployment happens for your organization, latest task version would be picked up. I’ll update the thread if things go south.

@jakubch1 could you please update the assignee for this issue? it seems @abhadauria1 does not work on this project anymore? Maybe @Haplois could take a look at this as he created this issue with his change https://github.com/microsoft/vstest/pull/3068

This issue is still occurring 22-months after the initial report:

2023-08-14T17:22:53.1189389Z Task : Visual Studio Test 2023-08-14T17:22:53.1189480Z Description : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test (VsTest) runner. Test frameworks that have a Visual Studio test adapter such as MsTest, xUnit, NUnit, Chutzpah (for JavaScript tests using QUnit, Mocha and Jasmine), etc. can be run. Tests can be distributed on multiple agents using this task (version 2). 2023-08-14T17:22:53.1189930Z Version : 2.224.0 2023-08-14T17:22:53.1189983Z Author : Microsoft Corporation 2023-08-14T17:22:53.1190063Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/test/vstest 2023-08-14T17:22:53.1190330Z ============================================================================== 2023-08-14T17:22:56.0000189Z Running tests using vstest.console.exe runner. 2023-08-14T17:22:56.0000747Z ====================================================== 2023-08-14T17:22:56.0001762Z Test selector : Test assemblies 2023-08-14T17:22:56.0002114Z Test filter criteria : TestCategory=Adhoc 2023-08-14T17:22:56.0002435Z Search folder : D:\a\1\s 2023-08-14T17:22:56.0237296Z Action when minimum tests threshold not met : donothing 2023-08-14T17:22:56.0237491Z Minimum tests expected to be run: 0 2023-08-14T17:22:56.2921144Z Run settings file : D:\a\1\s\QAAutomation\UITests\UiTests\bin\Release\net7.0\tst.edge.runsettings 2023-08-14T17:22:56.2922294Z Run in parallel : false 2023-08-14T17:22:56.2922609Z Run in isolation : false 2023-08-14T17:22:56.2922930Z Path to custom adapters : undefined 2023-08-14T17:22:56.2924324Z Other console options : /logger:trx;LogFileName=tst-edge-adhoc.trx /framework:“.NETCoreApp,Version=v7.0” 2023-08-14T17:22:56.2924736Z Code coverage enabled : false 2023-08-14T17:22:56.2925299Z Diagnostics enabled : false 2023-08-14T17:22:56.2929939Z Run the tests locally using vstest.console.exe 2023-08-14T17:22:56.2930121Z ======================================================== 2023-08-14T17:22:56.2930747Z Source filter: D:\a\1\s\QAAutomation\UITests\UITests\bin\Release\net7.0*tests.dll 2023-08-14T17:22:56.6963233Z ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work. 2023-08-14T17:22:56.7306337Z ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work. 2023-08-14T17:22:56.8691061Z ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work.

For what it’s worth, my workaround is to roll back to 16.11.0, which is the last release of the VS2019 test runner. It seems every version of the VS2022 test runner has the warnings.

Include the following in the pipeline (relevant items only; not a complete pipeline definition).

- task: VisualStudioTestPlatformInstaller@1
  inputs:
    packageFeedSelector: 'nugetOrg'
    versionSelector: 'specificVersion'
    testPlatformVersion: '16.11.0'

- task: VSTest@2
  inputs:
    vsTestVersion: 'toolsInstaller'

Edit: I just realized upon re-scanning the comments that this solution had already been offered a while ago. 🤷‍♂️

We have seen the same issue on our pipelines. For what its worth our build agent is using VS2019 and the pipeline is using the “Visual Studio test platform installer” task which was pulling the latest (v17) test tools that are for the upcoming release of VS2022