You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, CA1822 provides exclusions when attributes from XUnit, MSTest, and NUnit are applied to a method. I am in the process of migrating to TUnit, a new testing framework; but since it does not use the same attributes, [Test] methods are being flagged by CA1822.
It would be helpful to either/both:
have a parameter in the .editorconfig to add additional attributes to the skipped list
add TUnit.Core.TestAttribute, TUnit.Core.BeforeAttribute, TUnit.Core.BeforeEveryAttribute, TUnit.Core.AfterAttribute, TUnit.Core.AfterEveryAttribute` to the exclusion list.
Describe suggestions on how to achieve the rule
Am not familiar enough with the process to provide clear directions on how to improve. Expected .editorconfig might look something like:
Analyzer
Diagnostic ID: CA1822
Describe the improvement
Currently, CA1822 provides exclusions when attributes from XUnit, MSTest, and NUnit are applied to a method. I am in the process of migrating to TUnit, a new testing framework; but since it does not use the same attributes,
[Test]
methods are being flagged by CA1822.It would be helpful to either/both:
TUnit.Core.TestAttribute
,TUnit.Core.BeforeAttribute
,TUnit.Core.BeforeEveryAttribute,
TUnit.Core.AfterAttribute,
TUnit.Core.AfterEveryAttribute` to the exclusion list.Describe suggestions on how to achieve the rule
WellKnownTypeNames
Additional context
TUnit documentation: https://thomhurst.github.io/TUnit/docs/intro
The text was updated successfully, but these errors were encountered: