Verified Agent Skill record

Writing Mstest Tests

Use this Skill to fix, rewrite, improve, modernize, or explain existing MSTest tests and MSTest-specific configuration while matching the project’s installed MSTest version and established conventions. It covers assertion usage, data-driven tests, lifecycle and TestContext, timeout and cancellation, retry and environment conditions, cleanup, parallelization, MSTest.Sdk setup, and MSTESTxxxx diagnostics.

Tasks

Fix or rewrite existing MSTest assertions while preserving the test’s intended behavior and using expected-first, actual-second ordering for Assert.AreEqual.
Update existing MSTest tests or MSTest-specific configuration for version-compatible assertions, exception checks, data-driven tests, lifecycle, TestContext, timeout, cancellation, retry, cleanup, parallelization, OS or CI conditions, and MSTESTxxxx diagnostics.
Replace generic or unsafe existing checks with suitable MSTest assertions, including Boolean, collection, string, numeric, null, identity, type, exception, hard-cast, and object[] checks.
Explain or correct existing MSTest tests without designing new test cases, running tests, migrating frameworks, or creating project files.

Inputs

Code under test
Existing test code
Test scenario description

Outputs

Corrected MSTest code
Version-compatible MSTest assertion or configuration guidance
A brief explanation of the semantic reason for an assertion transformation

Limitations and checks

Do not use this Skill for designing new test cases from scratch; hand that work off to code-testing-agent while using this Skill only for MSTest API or version guidance.
Do not use this Skill for report-only audits, anti-pattern detection, flaky-test investigation, running tests, framework migration, CI/CD pipeline configuration, or project-file creation.
Do not use this Skill for xUnit, NUnit, TUnit, non-MSTest, or non-.NET code.
Do not copy an MSTest API example unless its documented minimum version is satisfied by the project.
ValueTuple DynamicData remains positional and swapping same-typed elements can still compile.
Do not assume the latest MSTest APIs.
Do not reverse comparison assertion arguments to mirror the source expression’s left-to-right order.
Check the test project, packages.config, assembly reference HintPath values, project SDK declaration, and global.json msbuild-sdks entries as applicable to determine the exact MSTest version and project system.