Skip to content

Fix MSTEST0001 (parallelization analyzer) to work with VSTest#6480

Merged
Evangelink merged 1 commit intomainfrom
dev/ygerges/parallel-analyzer
Sep 2, 2025
Merged

Fix MSTEST0001 (parallelization analyzer) to work with VSTest#6480
Evangelink merged 1 commit intomainfrom
dev/ygerges/parallel-analyzer

Conversation

@Youssef1313
Copy link
Copy Markdown
Member

Fixes #6467

Copy link
Copy Markdown
Member

@Evangelink Evangelink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Youssef1313

@Evangelink Evangelink merged commit 4920aff into main Sep 2, 2025
9 checks passed
@Evangelink Evangelink deleted the dev/ygerges/parallel-analyzer branch September 2, 2025 07:10
@Youssef1313
Copy link
Copy Markdown
Member Author

/backport to rel/3.10

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Sep 2, 2025

Started backporting to rel/3.10: https://github.com/microsoft/testfx/actions/runs/17396351123

@jeroenjanssen-cpp
Copy link
Copy Markdown

I am using VSTest in some projects and I am upgrading from 3.11.0 to 4.0.0 today and got a lot of MSTEST0001 errors.
I could not find this in the release notes for 4.0.0 at https://github.com/microsoft/testfx/releases/tag/v4.0.0

@Youssef1313
Copy link
Copy Markdown
Member Author

This PR is already part of 3.11.
What probably affects you is that it's now enabled by default. You can turn it off by adding <NoWarn>$(NoWarn);MSTEST0001</NoWarn>, or set it off in .globalconfig, or alternatively keep it on and address the warning.

@jeroenjanssen-cpp
Copy link
Copy Markdown

Can you please add to the v4.0.0 release notes/documentation that it is enabled by default? (so other people also know about this)

It is also not mentioned in the migration guide from v3 to v4 at https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-mstest-migration-v3-v4

@Youssef1313
Copy link
Copy Markdown
Member Author

Updating the migration guide in dotnet/docs#48969

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mstest0001 rule does not work?

3 participants