Skip to content

Update default severity change in MSTest 3.10 #47551

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 24, 2025
Merged

Update default severity change in MSTest 3.10 #47551

merged 1 commit into from
Jul 24, 2025
+2 −2

Conversation

Evangelink
Copy link
Member

@Evangelink Evangelink commented Jul 23, 2025 •
edited by github-actions bot
Loading

Summary

With the release of MSTest 3.10, some analyzers will have their severity bumped to Warning by default. Reflect this change in documentation.

Internal previews

📄 File 🔗 Preview link
docs/core/testing/mstest-analyzers/mstest0006.md MSTEST0006: Avoid [ExpectedException]
docs/core/testing/mstest-analyzers/mstest0039.md "MSTEST0039: Use newer 'Assert.Throws' methods"

@Evangelink Evangelink requested review from IEvangelist and a team as code owners July 23, 2025 20:00
@dotnetrepoman dotnetrepoman bot added this to the July 2025 milestone Jul 23, 2025
@Evangelink Evangelink enabled auto-merge (squash) July 23, 2025 20:01
@Evangelink Evangelink merged commit e78996d into main Jul 24, 2025
12 checks passed
@Evangelink Evangelink deleted the dev/amauryleve/mstest-310-bump branch July 24, 2025 03:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Youssef1313 Youssef1313 Youssef1313 approved these changes

@IEvangelist IEvangelist Awaiting requested review from IEvangelist IEvangelist is a code owner

Assignees
No one assigned
Labels
dotnet-fundamentals/svc
Projects
None yet
Milestone
July 2025
Development

Successfully merging this pull request may close these issues.
2 participants
@Evangelink @Youssef1313