Use namespace-based test detection for more flexible test framework support

Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>

Author: Copilot

IntelliTect.Analyzer/IntelliTect.Analyzer/Analyzers/NamingMethodPascal.cs

@@ -108,26 +108,41 @@ private static void AnalyzeSymbol(SymbolAnalysisContext context)
 
         private static bool IsTestMethod(IMethodSymbol methodSymbol)
         {
-            // Common test framework attributes
-            string[] testAttributeNames = 
+            // Test framework namespaces - checking namespace is more flexible than specific attribute names
+            string[] testFrameworkNamespaces = 
             [
-                "TestMethod",      // MSTest
-                "TestMethodAttribute",
-                "Fact",            // xUnit
-                "FactAttribute",
-                "Theory",          // xUnit
-                "TheoryAttribute",
-                "Test",            // NUnit
-                "TestAttribute",
-                "TestCase",        // NUnit
-                "TestCaseAttribute",
-                "TestCaseSource",  // NUnit
-                "TestCaseSourceAttribute"
+                "Xunit",                                    // xUnit
+                "NUnit.Framework",                          // NUnit
+                "Microsoft.VisualStudio.TestTools.UnitTesting",  // MSTest
+                "TUnit.Core"                                // TUnit
             ];
 
             ImmutableArray<AttributeData> attributes = methodSymbol.GetAttributes();
             return attributes.Any(attribute =>
-                attribute.AttributeClass?.Name is string name && testAttributeNames.Contains(name));
+            {
+                if (attribute.AttributeClass == null)
+                {
+                    return false;
+                }
+
+                // Check namespace first (more robust for production code)
+                string containingNamespace = attribute.AttributeClass.ContainingNamespace?.ToDisplayString();
+                if (containingNamespace != null && 
+                    testFrameworkNamespaces.Any(ns => containingNamespace.StartsWith(ns, StringComparison.Ordinal)))
+                {
+                    return true;
+                }
+
+                // Fallback: check attribute name for common test attributes
+                // This helps in test environments where namespace metadata may be incomplete
+                string attributeName = attribute.AttributeClass.Name;
+                return attributeName == "TestMethod" || attributeName == "TestMethodAttribute" ||
+                       attributeName == "Fact" || attributeName == "FactAttribute" ||
+                       attributeName == "Theory" || attributeName == "TheoryAttribute" ||
+                       attributeName == "Test" || attributeName == "TestAttribute" ||
+                       attributeName == "TestCase" || attributeName == "TestCaseAttribute" ||
+                       attributeName == "TestCaseSource" || attributeName == "TestCaseSourceAttribute";
+            });
         }
     }
 }

docs/analyzers/00XX.Naming.md

@@ -49,7 +49,7 @@ class SomeClass
 
 Methods, including local functions, should be PascalCase
 
-**Note:** Test methods decorated with test framework attributes (e.g., `[TestMethod]`, `[Fact]`, `[Theory]`, `[Test]`) are exempt from this rule, as they commonly use underscores for readability (e.g., `Method_Scenario_ExpectedResult`).
+**Note:** Test methods decorated with test framework attributes from xUnit, NUnit, MSTest, or TUnit are exempt from this rule, as they commonly use underscores for readability (e.g., `Method_Scenario_ExpectedResult`). Any attribute from these framework namespaces will be recognized automatically.
 
 **Allowed**
 ```c#