Writing MSTest Tests skill: what it does and how to install it
Improves existing MSTest tests with version-aware assertions, data-driven patterns, lifecycle handling and fixes for MSTESTxxxx diagnostics.
Summary generated from the skill's documentation.
Install
$ npx skills add dotnet/skills --skill writing-mstest-testsRun it in a terminal. If your agent is already running, start a new session so it picks the skill up.
About this skill
What it does. Checks the installed MSTest version and project setup, then rewrites existing tests with compatible assertions, data-driven patterns, lifecycle, cancellation, timeout and condition handling. It also covers MSTESTxxxx diagnostics and repository-specific conventions, and verifies edited tests when execution is allowed.
When to use it. Use it to fix, update, modernise or explain existing MSTest tests and configuration. It does not design new test cases, run tests, migrate MSTest versions, configure CI/CD, or handle other .NET test frameworks.
History
Repo stars
5.6kAbout +410 since 9 Jul 2026
Before 1 Oct 2026 the curve is estimated from public event data.
Stars are counted for the whole repository, which holds 43 skills.
Show as a table
| Date | Repo stars |
|---|---|
| 5 Oct 2026 | 5,557 |
| 4 Oct 2026 | 5,551 |
| 3 Oct 2026 | 5,543 |
| 2 Oct 2026 | 5,540 |
| 1 Oct 2026 | 5,531 |
| 24 Sept 2026 (estimated) | 5,519 |
| 17 Sept 2026 (estimated) | 5,494 |
| 10 Sept 2026 (estimated) | 5,419 |
| 3 Sept 2026 (estimated) | 5,258 |
| 27 Aug 2026 (estimated) | 5,233 |
| 20 Aug 2026 (estimated) | 5,221 |
| 13 Aug 2026 (estimated) | 5,221 |
| 6 Aug 2026 (estimated) | 5,171 |
| 30 Jul 2026 (estimated) | 5,159 |
| 23 Jul 2026 (estimated) | 5,159 |
| 16 Jul 2026 (estimated) | 5,147 |
| 9 Jul 2026 (estimated) | 5,147 |
Installs
2.6k
Tracking since . A chart appears once there are 7 days of data.
Installs via skills.sh
Similar skills
- Skill CreatorCreates new skills, improves existing ones and measures how well they perform with evals and benchmarks.
- Test-Driven DevelopmentMakes the agent write a failing test before any implementation code, for features and bug fixes alike.
- Source-Driven DevelopmentChecks every implementation decision against official documentation, so the code cites its sources and avoids outdated patterns.