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
{{ message }}
Repository navigation
Commit 732c8d0
Browse filesBrowse the repository at this point in the historyBrowse files
Use real framework assemblies and data-driven tests for INTL0003 exemption
- Add xunit.v3.core, NUnit, TUnit.Core as compile+runtime references in test project
(PrivateAssets=all so no runner conflicts; IncludeAssets=compile;runtime for DLL availability)
- Create TestFrameworkReferences registry: single source of truth for all supported
test frameworks (name, attribute syntax, using directive, MetadataReference).
Adding a new framework only requires one entry here + the namespace in NamingMethodPascal.
- Inject all framework references into every DiagnosticVerifier.Helper CreateProject
compilation, so namespace-based detection is exercised by real tests (not just fallback)
- Collapse 4 redundant framework-specific test methods into one [DynamicData] test
driven by TestFrameworkReferences.All; new frameworks auto-covered at zero cost
- Add negative test: non-test method with underscores in a test class still warns
- Add user-defined [Test] attribute test: custom namespace attribute still warns
- Fix IsTestMethod fallback: gate name-based matching on TypeKind.Error only,
preventing false negatives for user-defined attributes named Test/Fact/Theory/etc.
- Make testFrameworkNamespaces and commonTestAttributeNames static readonly fields
to avoid per-invocation heap allocation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments