Is there a way suppress the CA1822 when using UnityTestAttribute?

[watsonsong]

The IDE will report CA1822 issue when using the Microsoft.CodeAnalysis.NetAnalyzers and mark the unity test as [UnityTest]. But the [Test] will be correctly recognized.
This is not a problem, just wonder whether there has a proper way to avoid this issue.

CA1822 (Mark member as static) fires for almost every unit test

[superpig]

From looking at the fix to that issue, unfortunately it looks like they solved the problem by hardcoding a list of particular attributes that silence the analyser…

You can try putting both attributes on your test, i.e. [UnityTest, Test] - I think that will silence the analyser warnings and won’t affect the way the test runs, though unfortunately for me in Rider this seems to just introduce a different warning about ‘NUnit Test attribute should provide expected result for test method with return value.’

[watsonsong]

@superpig

From looking at the fix to that issue, unfortunately it looks like they solved the problem by hardcoding a list of particular attributes that silence the analyser…

You can try putting both attributes on your test, i.e. [UnityTest, Test] - I think that will silence the analyser warnings and won’t affect the way the test runs, though unfortunately for me in Rider this seems to just introduce a different warning about ‘NUnit Test attribute should provide expected result for test method with return value.’

I first add ‘Test’ before ‘UnityTest’, but the coroutine is not execute correctly. I wonder if the logic depend on the sequencial order is correct and robust way.