filter-syntax

Translate VSTest test selection filters to MTP and xUnit v3 syntaxes.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill filter-syntax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: filter-syntax
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/filter-syntax
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill filter-syntax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates confusion about how test-filter expressions differ across .NET test runners and frameworks, so you can consistently select the right tests to run.

Core Features & Use Cases

  • VSTest filter syntax reference: covers the <Property><Operator><Value>[|&<Expression>] grammar and supported properties for MSTest, NUnit, and xUnit v2.
  • MTP filter syntax guidance: explains how the same filter concept maps to MSTest/NUnit-on-MTP versus xUnit v3-on-MTP (different flags) and TUnit path-based filters.
  • VSTest → MTP translation rules: provides concrete mappings for common filter patterns, including when to use xUnit v3 query filter language.

Quick Start

Use filter-syntax to translate your current dotnet test --filter ... expression into the correct MTP or xUnit v3 flags needed for your test runner.

Frequently Asked Questions about filter-syntax

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

FAQPage Schema
How do I write VSTest filter expressions for MSTest, NUnit, or xUnit v2?

VSTest filter expressions use a `<Property><Operator><Value>[|&<Expression>]` grammar to target specific test classes, methods, namespaces, or traits. This syntax applies consistently to MSTest, NUnit, and xUnit v2 test runners.

What is the correct MTP filter syntax for xUnit v3?

MTP filter syntax for xUnit v3 requires using different flags compared to MSTest or NUnit-on-MTP. You must apply specific xUnit v3 query filter language rules to target tests correctly without manual guesswork.

How do I translate VSTest test filters to MTP flags during a CI migration?

To translate VSTest test filters to MTP flags during a CI migration, apply deterministic mapping rules for common filter patterns. This ensures your test selection logic remains consistent when moving between runners.

Does MTP filter syntax work the same way for MSTest, NUnit, and TUnit?

MTP filter syntax does not work uniformly across all frameworks. While MSTest and NUnit-on-MTP share similar flag concepts, TUnit relies on path-based filters, and xUnit v3-on-MTP requires distinct query filter handling.

Why does my dotnet test filter expression fail to select specific test methods?

Your dotnet test filter expression may fail due to incorrect property or operator combinators for your specific runner. You must resolve incompatibilities by applying the correct VSTest or MTP syntax for your target framework.

Can I use VSTest property and operator combinators to target test traits and categories?

Yes, you can use VSTest-style property and operator combinators to deterministically target traits, categories, namespaces, and priority values. This ensures precise test selection during local runs and CI migrations.