[Question]: vstest@2 vs vstest@3

Task name

vstest

Task version

No response

Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[X] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows 11

Question

Hi,

What is going on with vstest task versioning? It seems that they are two separate versions existing and in support at the same time. In last 6 months vstest@2 got:

Vstest zip uploads with Prod storage account (#19921)
Rebuild tasks and remove mockery from node modules [Part 2] (#19731)
[VsTestV2/V3] Update node version to 20.11.0 (#19687)
Updated VsTestV2 task to version 2.237.0 (#19663)
Updated VsTestV2 task to version to 2.236.0 (#19617)
Fix VsTestV2 empty line at end of package-lock.json (#19542)
Fixing Warning for older version of TestPlat (#19488)
update task version for vstest V2 from 2.229.0 to 2.234.0 (#19464)
Migrate 4 tasks to Node20 (#19215)

while vstest@3 got:

Rebuild tasks and remove mockery from node modules [Part 2] (#19731)
[VsTestV2/V3] Update node version to 20.11.0 (#19687)
Migrate 4 tasks to Node20 (#19215)

Issues like https://github.com/microsoft/azure-pipelines-tasks/pull/19488 are still existing on @3 while being solved on @2. The @3 was created over 2 years ago, so there can be a lot of discrepancies between those tasks.

Should I abandon @3 and go with @2 as it seems better looked after, or what is the actual purpose of @3?

microsoft / azure-pipelines-tasks