What problem does it solve? Test filter syntax differs across platforms (VSTest vs Microsoft Testing Platform) and frameworks (MSTest, NUnit, xUnit v2/v3, TUnit), making it easy to write invalid filter expressions when running or migrating .NET tests. This Skill supplies the correct syntax for every combination so agents and developers select the right tests without trial and error. ## Core Features & Use Cases - VSTest filter reference: Documents --filter expression operators, combinators, and supported properties for MSTest, xUnit v2, and NUnit. - MTP filter coverage: Details MSTest/NUnit filters, xUnit v3 framework-specific flags (--filter-class, --filter-method, --filter-trait), the xUnit v3 query filter language, and TUnit --treenode-filter path syntax. - VSTest-to-MTP translation: Provides a mapping table for converting VSTest filter expressions to xUnit v3 native MTP equivalents during migration. - Use Case: When migrating a test suite from VSTest to Microsoft Testing Platform with xUnit v3, look up how to translate FullyQualifiedName~ClassName into --filter-class *ClassName* with correct wildcard handling. ## Quick Start Ask the agent to show the correct dotnet test filter syntax for running only integration-category tests in an xUnit v3 project on Microsoft Testing Platform.