Detects the .NET test platform and runs dotnet test with correct filter syntax.
npx skills add https://github.com/D1ssolve/craft-agents --skill run-tests-d1ssolve
Please help me install this Agent Skill. Skill: run-tests Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/run-tests Command: npx skills add https://github.com/D1ssolve/craft-agents --skill run-tests-d1ssolve
dotnet test invocation so you avoid argument mixups like --logger trx versus --report-trx. ## Core Features & Use Cases - Platform Detection: Reads global.json, .csproj, Directory.Build.props, and Directory.Packages.props to determine whether a project uses VSTest or MTP and which SDK version applies. - Correct Command Construction: Applies the right syntax for each combination, including the -- separator rules on SDK 8/9 versus direct MTP arguments on SDK 10+. - Framework-Aware Filtering: Translates test categories into the proper filter syntax for MSTest, xUnit v2/v3, NUnit, and TUnit (--filter, --filter-class, --filter-trait, --treenode-filter). - Use Case: You ask to run only the integration tests in a multi-TFM xUnit v3 project on .NET 10. The Skill detects MTP from global.json, then runs dotnet test --project <path> --framework net9.0 --filter-trait "Category=Integration" instead of the whole suite. ## Quick Start Run only the integration tests in my .NET project using the correct dotnet test command for my setup.High-intent search queries and answers about installing and using this skill.
Use `dotnet test --filter "<expression>"` for VSTest projects with operators like `=`, `!=`, and `~`. On Microsoft.Testing.Platform, MSTest and NUnit keep the same `--filter` syntax, while xUnit v3 uses `--filter-class`, `--filter-method`, and `--filter-trait`, and TUnit uses `--treenode-filter`.
Check `global.json` for `"test": { "runner": "Microsoft.Testing.Platform" }` on .NET SDK 10+, or look for `<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>` in `.csproj` or `Directory.Build.props` on SDK 8/9. If neither signal is present, the project uses VSTest.
`--logger trx` is the VSTest flag for generating TRX result files, while `--report-trx` is the Microsoft.Testing.Platform equivalent and requires the Microsoft.Testing.Extensions.TrxReport package. Using the wrong flag for your platform causes an unrecognized option error.
No. On .NET SDK 10+, MTP arguments are passed directly, for example `dotnet test --project . --report-trx`. The `--` separator is only required on .NET SDK 8 and 9 when bridging to Microsoft.Testing.Platform.
This usually means the filter syntax does not match the platform or framework, such as using VSTest expression syntax with xUnit v3 on MTP. Verify the correct filter flags for your framework and confirm property names like `TestCategory` for MSTest versus `Category` traits for xUnit.
Pass `--framework <TFM>` to `dotnet test`, for example `dotnet test --framework net8.0`, when the project uses `<TargetFrameworks>` with multiple monikers. This flag is consumed by dotnet test itself and always goes before the `--` separator on SDK 8/9.
ojrojasIdentifies.NET test frameworks and compares their assertion APIs, skipping patterns, and setup/teardown methods.
raandreeDiagnose Sampler-based PowerShell build and Pester 5 test failures.
FittyArDetects the .NET test platform and test framework from project configuration files.
NotMyselfConfigure MSTest projects to use Microsoft.Testing.Platform in .NET 10.