Run MaterialDesignInXamlToolkit tests correctly with dotnet test, TUnit, and Microsoft Testing Platform. Use when validating changes, choosing a safe test scope, or filtering to the exact affected tests.
Use this skill when you need to run or suggest test commands in this repository.
UseMicrosoftTestingPlatformRunner=true.TestingPlatformDotnetTestSupport=true.global.json does not opt into test.runner = Microsoft.Testing.Platform.dotnet test in the legacy CLI mode while delegating execution to MTP-backed test applications.--.dotnet test --filter ... for these projects.MaterialDesignThemes.UITestsTUnit uses --treenode-filter.
Format:
/<Assembly>/<Namespace>/<Class>/<Test>
* as a wildcard within a segment.(A)|(B) inside a segment for OR.--minimum-expected-tests <n> so an empty selection fails loudly.dotnet test tests\MaterialDesignThemes.Wpf.Tests\MaterialDesignThemes.Wpf.Tests.csproj -c Release --no-build -- --treenode-filter "/*/*/AutomationPropertiesNameConverterTests/*" --minimum-expected-tests 1 --no-ansi --no-progress
dotnet test tests\MaterialDesignThemes.UITests\MaterialDesignThemes.UITests.csproj -c Release --no-build -- --treenode-filter "/*/*/DecimalUpDownTests/(NumericButtons_WithMaximum_DisablesPlusButton)|(NumericButtons_WithMinimum_DisablesMinusButton)" --minimum-expected-tests 2 --no-ansi --no-progress
tests\MaterialDesignThemes.UITests\bin\Release\net10.0-windows\MaterialDesignThemes.UITests.exe --list-tests --no-ansi --treenode-filter "/*/*/DecimalUpDownTests/(NumericButtons_WithMaximum_DisablesPlusButton)|(NumericButtons_WithMinimum_DisablesMinusButton)"
dotnet test --filter ... for these MTP-backed projects.--.--minimum-expected-tests, which can hide a bad filter.global.jsontests/MaterialDesignThemes.Wpf.Tests/MaterialDesignThemes.Wpf.Tests.csprojtests/MaterialDesignThemes.UITests/MaterialDesignThemes.UITests.csproj