Add code fix for MSTEST0031 — `DoNotUseSystemDescriptionAttribute`

[Evangelink]

Priority: High
Estimated Effort: Small

DoNotUseSystemDescriptionAttributeAnalyzer warns when [System.ComponentModel.Description("...")] is applied to a test method (instead of MSTest's own description mechanism). A code fix can automatically replace [Description("text")] (with using System.ComponentModel) with [TestMethod(DisplayName = "text")] or the appropriate MSTest description attribute.

File to create: src/Analyzers/MSTest.Analyzers.CodeFixes/DoNotUseSystemDescriptionAttributeFixer.cs

[github-actions]

---

Note

The pull request was not created — a fallback review issue was created instead due to protected file changes: #7910

🤖 This is an automated response from Test Improver.

When the code fix for MSTEST0031 (DoNotUseSystemDescriptionAttribute) is implemented, the test file DoNotUseSystemDescriptionAttributeAnalyzerTests.cs will need to be updated to test the fix path. Here's what the test coverage should include once the fixer is available:

1. Switch the VerifyCS alias from EmptyCodeFixProvider to the new DoNotUseSystemDescriptionAttributeFixer.

2. Code fix transformation tests (with VerifyCS.VerifyCodeFixAsync):

   • [System.ComponentModel.Description("text")] on a [TestMethod] → fixed to [TestMethod(DisplayName = "text")] (if that's the chosen replacement)
   • Case where the using System.ComponentModel; directive needs to be removed after replacement
   • Case where description is applied to multiple test methods
   • Case where description is applied alongside other attributes

3. No-op test: verify the fix is not offered for non-test methods (the diagnostic doesn't fire there, so no fix is needed).

The pattern to follow is the same as StringAssertToAssertAnalyzerTests.cs (which includes both analyzer diagnostics and VerifyCodeFixAsync transformations).

Happy to add the code fix tests once the fixer implementation lands. 🎯

Note

🔒 Integrity filter blocked 14 items

The following items were blocked because they don't meet the GitHub integrity level.

• #7680 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #3499 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #4931 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7542 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #6950 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #6335 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #6760 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7468 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7340 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7045 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #6611 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7908 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7846 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7773 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Daily Test Improver · ● 7.1M · ◷