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
When there's a Test namespace based on project name with .Test in it, and follow up namespace Something, and there's a using importing the Something directly, raise an issue to use .Test suffix instead.
using SonarAnalyzer.Xxx.Something;
namespace SonarAnalyzser.Xxx.Test.Something // Noncompliant
namespace SonarAnalyzser.Xxx.Something.Test// Compliant, the using can be removed (we don't care in this rule)
We don't want to raise everywhere to reduce noise. For example :
namespace SonarAnalyzer.Enterprise.SymbolicExecution.Test.TestFramework; // This still makes sense as is
namespace SonarAnalyzer.Test.Rules; // This is acceptable
The text was updated successfully, but these errors were encountered:
When there's a Test namespace based on project name with
.Test
in it, and follow up namespaceSomething
, and there's ausing
importing theSomething
directly, raise an issue to use.Test
suffix instead.We don't want to raise everywhere to reduce noise. For example :
The text was updated successfully, but these errors were encountered: