writing-mstest-tests
F-U-S-E-E/FuseDevelopmentGroupBest practices for writing new MSTest 3.x/4.x unit tests and implementing concrete fixes in existing MSTest code. Use when the user asks to write, create,…
Scores out of 100 · grade B+
2026-08-18Works
40% of the score100/100
- Loads cleanly: valid frontmatter, required fields present, no dangling references.
Maintained
25% of the score100/100
- no commits in the last 12 weeks
Adopted
20% of the score13/100
- 8 stars on the source repo.
Documented
15% of the score81/100
- 1,384 words with worked examples.
Install
npx skills add F-U-S-E-E/FuseDevelopmentGroup/writing-mstest-testsWhat it says it does
Best practices for writing new MSTest 3.x/4.x unit tests and implementing concrete fixes in existing MSTest code. Use when the user asks to write, create, implement, repair, or modernize tests (including fix-it prompts such as 'something seems off, fix issues'). Primary fit for direct code changes like correcting swapped Assert.AreEqual argument order, replacing outdated assertion patterns, and converting DynamicData from IEnumerable<object[]> to ValueTuple-based data sets. Covers modern assertions, data-driven tests, test lifecycle, MSTest.Sdk, sealed classes, Assert.Throws, DynamicData with ValueTuples, TestContext, and conditional execution. Do NOT use for broad test quality audits, flaky-test investigations, or test smell detection reports — use test-anti-patterns instead.
Also in F-U-S-E-E/FuseDevelopmentGroup
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| analyzing-dotnet-performanceF-U-S-E-E/FuseDevelopmentGroup | clean | Skill | 8 stars | today | |
| apple-crash-symbolicationF-U-S-E-E/FuseDevelopmentGroup | clean | Skill | 8 stars | today | |
| clr-activation-debuggingF-U-S-E-E/FuseDevelopmentGroup | clean | Skill | 8 stars | today | |
| coverage-analysisF-U-S-E-E/FuseDevelopmentGroup | clean | Skill | 8 stars | today | |
| directory-build-organizationF-U-S-E-E/FuseDevelopmentGroup | clean | Skill | 8 stars | today | |
| dotnet-aot-compatF-U-S-E-E/FuseDevelopmentGroup | clean | Skill | 8 stars | today |
Other testing & qa skills
Browse all| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| skill-creatoranthropics/skills | No license | Testing & QA | 358,827 installs | today | |
| systematic-debuggingobra/superpowers | clean | Testing & QA | 232,863 installs | 2 days ago | |
| webapp-testinganthropics/skills | No license | Testing & QA | 138,299 installs | today | |
| test-driven-developmentobra/superpowers | clean | Testing & QA | 204,536 installs | 2 days ago | |
| migrate-to-shoehornmattpocock/skills | clean | Testing & QA | 238,622 installs | today | |
| playwright-component-testingmicrosoft/playwright | clean | Testing & QA | 95k stars | today |
Put this measurement in your README
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=F-U-S-E-E%2FFuseDevelopmentGroup)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.
