filter-syntax

Provides test filter syntax reference for VSTest and Microsoft Testing Platform across .NET test frameworks.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Netcodr81/kinetic-reports --skill filter-syntax-netcodr81
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: filter-syntax
Source: https://github.com/Netcodr81/kinetic-reports/tree/main/.github/skills/filter-syntax
Command: npx skills add https://github.com/Netcodr81/kinetic-reports --skill filter-syntax-netcodr81

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing correct test filter expressions is error-prone because syntax differs across platforms (VSTest vs. Microsoft Testing Platform) and frameworks (MSTest, NUnit, xUnit v2/v3, TUnit). This Skill supplies the exact filter syntax for every combination so AI agents and developers select and run the right tests without guessing. ## Core Features & Use Cases - VSTest Filter Reference: Documents --filter expression syntax, operators (=, !=, ~, !~), combinators, and supported properties per framework. - MTP Filter Coverage: Details MSTest/NUnit filters, xUnit v3 framework-specific flags (--filter-class, --filter-method, --filter-trait), the xUnit query filter language, and TUnit --treenode-filter path syntax. - VSTest-to-MTP Translation: Provides a mapping table for migrating VSTest filter expressions to xUnit v3 native MTP equivalents. - Use Case: When an agent running tests needs to execute only integration tests in a specific namespace for an xUnit v3 project, it loads this reference to construct the correct --filter-namespace and --filter-trait flags. ## Quick Start Ask the AI to run only the smoke tests in your xUnit v3 project and it will use this reference to build the correct filter command.

Frequently Asked Questions about filter-syntax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter tests with dotnet test --filter?▼

Use the syntax dotnet test --filter "<Property><Operator><Value>" with operators =, !=, ~, and !~, combined using & for AND and | for OR. For example, dotnet test --filter "TestCategory=Integration" runs only tests in that category.

How to filter xUnit v3 tests on Microsoft Testing Platform?▼

xUnit v3 on MTP uses framework-specific flags like --filter-class, --filter-method, --filter-namespace, and --filter-trait instead of the generic --filter expression. For complex cases, use --filter-query with the xUnit query filter language.

Does VSTest filter syntax work on Microsoft Testing Platform?▼

MSTest, NUnit, and xUnit v2 keep the same --filter syntax on MTP, so no changes are needed. xUnit v3 does not support VSTest --filter syntax on MTP and requires its native filter flags or query language instead.

How do I filter TUnit tests by category or property?▼

TUnit uses --treenode-filter with a path syntax like "/<Assembly>/<Namespace>/<ClassName>/<TestName>" supporting wildcards. Append property conditions such as [Category=Smoke] or [Category!=Slow] to filter by custom properties.

How to translate VSTest filters to xUnit v3 MTP equivalents?▼

Map FullyQualifiedName~ClassName to --filter-class *ClassName*, Name=MethodName to --filter-method *MethodName*, and trait filters to --filter-trait "Category=Value". Complex expressions translate to --filter-query using the xUnit query filter language.