Agent skill · Testing & QA

filter-syntax

Reference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need filter syntax.

dotnetgithub.com/dotnetGitHub ↗
claude-codeMIT
Install
npx skills add dotnet/skills --skill filter-syntax --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: plugins/dotnet-test/skills/filter-syntax/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,927
Language: C#
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Test Filter Syntax Reference Filter syntax depends on the **platform** and **test framework**. ## VSTest filters (MSTest, xUnit v2, NUnit on VSTest) ```bash dotnet test --filter <EXPRESSION> ``` Expression syntax: `<Property><Operator><Value>[|&<Expression>]` **Operators:** | Operator | Meaning | |----------|---------| | `=` | Exact match | | `!=` | Not exact match | | `~` | Contains | | `!~` | Does not contain | **Combinators:** `|` (OR), `&` (AND). Parentheses for grouping: `(A|B)&C` **Supported properties by framework:** | Framework | Properties | |-----------|-----------| | MSTest | `FullyQualifiedName`, `Name`, `ClassName`, `Priority`, `TestCategory` | | xUnit | `FullyQualifiedName`, `DisplayName`, `Traits` | | NUnit | `FullyQualifiedName`, `Name`, `Priority`, `TestCategory` | An expression without an operator is treated as `FullyQualifiedName~<value>`. **Examples (VSTest):** ```bash # Run tests whose name contains "LoginTest" dotnet test --filter "Name~LoginTest" # Run a specific test class dotnet test --filter "ClassName=MyNamespace.MyTestClass" # Run tests in a category dotnet test --filter "TestCategory=Integration" # Exclude a category dotnet test --filter "TestCategory

What's inside
Steps it walks through
  1. VSTest filters (MSTest, xUnit v2, NUnit on VSTest)
  2. MTP filters — MSTest and NUnit
  3. MTP filters — xUnit (v3)
  4. xUnit v3 query filter language
  5. MTP filters — TUnit
  6. VSTest → MTP filter translation (for migration)
Commands it runs
dotnet test --filter <EXPRESSION>
Run tests whose name contains "LoginTest"
dotnet test --filter "Name~LoginTest"
Run a specific test class
dotnet test --filter "ClassName=MyNamespace.MyTestClass"
Run tests in a category
dotnet test --filter "TestCategory=Integration"
Exclude a category
dotnet test --filter "TestCategory!=Slow"
dotnet test --filter "ClassName=MyNamespace.MyTestClass&TestCategory=Unit"
More from skills
All skills →
find-untested-sourcesMANDATORY for static requests to find, identify, or list untested source files or modules, sources…Testing & QAdotnet-pinvokeCorrectly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function…Documentationmsbuild-antipatternsDetect and fix MSBuild anti-patterns in project and build files. USE WHEN asked to review, audit…Securityauthoring-github-workflowsAuthor and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a…DevOps & Cloudcreate-custom-agentCreates VS Code custom agent files (.agent.md) for specialized AI personas with tools…AI & Agentsmigrate-dotnet9-to-dotnet10Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes. USE FOR…Backend & API
About this skill
What does the filter-syntax skill do?

Reference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need filter syntax.

How do I install it?

Run `npx skills add dotnet/skills --skill filter-syntax --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dotnet/skills, a repository with 4,927 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.