Add TestCategories property to ITestDataRow for per-test-case categorization

[Copilot]

This PR adds support for applying test categories to individual test data rows in parameterized tests, addressing a long-standing user request for more granular test categorization.

Changes

Core API Changes

• Added TestCategories property to ITestDataRow interface
• Implemented TestCategories property in TestDataRow<T> class with [DataMember] attribute
• Property is nullable to maintain backward compatibility

Discovery Logic Updates

• Updated TestDataSourceHelpers.TryHandleITestDataRow() to extract test categories from test data rows
• Added backward-compatible overload to maintain existing API
• Modified discovery logic in AssemblyEnumerator to merge test categories from test data rows with existing method/class/assembly level categories

Usage Example

[TestMethod]
[DynamicData(nameof(GetTestData), DynamicDataSourceType.Method)]
public void MyParameterizedTest(string input, string expected)
{
    Assert.AreEqual(expected, ProcessInput(input));
}

public static IEnumerable<object[]> GetTestData()
{
    // Fast unit test case
    yield return new TestDataRow<(string, string)>(("input1", "output1"))
    {
        TestCategories = new List<string> { "Unit", "Fast" },
        DisplayName = "Fast unit test"
    };
    
    // Slow integration test case
    yield return new TestDataRow<(string, string)>(("input2", "output2"))
    {
        TestCategories = new List<string> { "Integration", "Slow" },
        DisplayName = "Integration test"
    };
}

Benefits

• Granular filtering: Can now filter tests by categories applied to individual test cases
• Mixed scenarios: Single test method can contain both unit tests and integration tests with appropriate categories
• Category inheritance: Test data row categories are merged with method/class/assembly level categories
• Backward compatibility: Existing code continues to work unchanged

Test Coverage

• Added comprehensive unit tests for TestDataRow and TestDataSourceHelpers
• Added integration tests to verify end-to-end functionality
• Created sample test project demonstrating real-world usage
• Validated category filtering works correctly with test discovery

This enables scenarios like:

# Run only fast test cases
dotnet test --filter "TestCategory=Fast"

# Run only integration test cases  
dotnet test --filter "TestCategory=Integration"

Fixes #4089.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• 5rqvsblobprodcus385.vsblob.vsassets.io
  • Triggering command: /home/REDACTED/work/testfx/testfx/.dotnet/dotnet msbuild /m /nologo /clp:Summary /v:quiet /nr:true /warnaserror /p:TreatWarningsAsErrors=true /p:ContinuousIntegrationBuild=false /home/REDACTED/work/testfx/testfx/artifacts/toolset/restore.proj /t:__WriteToolsetLocation /clp:ErrorsOnly;NoSummary /p:__ToolsetLocationOutputFile=/home/REDACTED/work/testfx/testfx/artifacts/toolset/10.0.0-beta.25316.2.txt (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.