Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dotnet/migrate-mstest-v1v2-to-v3
Migrate MSTest v1/v2 projects to MSTest v3, and fix v1/v2-to-v3 breaking changes that surface after the packages are already at 3.x. USE FOR: removing v1 Microsoft.VisualStudio.QualityTools.UnitTestFramework assembly references; moving MSTest.TestFramework/TestAdapter 1.x-2.x to 3.x, the MSTest metapackage, or MSTest.Sdk; tests that broke after a 2.x-to-3.x bump -- CS0411/CS1503 on Assert.AreEqual/AreNotEqual/AreSame once the object overloads became generic, and DataRow strict type matching (1L
1 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 1 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Our test projects are currently running on MSTest version 3.8.0 with no build errors or legacy settings files. We want to upgrade the entire test suite to MSTest v4. Please proceed with updating our package references and fixing any v4 breaking changes across the workspace.
| Checked | Without skill | With skill |
|---|---|---|
| Declines performing the MSTest v4 upgrade. | Missed | Passed |
| Refers to the dedicated MSTest v3-to-v4 migration skill. | Missed | Passed |
The instructions your model reads when the skill loads.
Migrate a test project from MSTest v1 (assembly references) or MSTest v2 (NuGet 1.x-2.x) to MSTest v3. MSTest v3 is not binary compatible with v1/v2 -- libraries compiled against v1/v2 must be recompiled.
Inspect the supplied workspace and classify v1, v2, partially migrated v3, or already-complete v3 before answering. Do not search the web or answer from memory first. For an edit request, continue through the requested source changes and validation; for an advice request, answer directly after the classification.
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll (MSTest v1)MSTest.TestFramework / MSTest.TestAdapter NuGet 1.x or 2.x.testsettings with .runsettings.testsettings / <LegacySettings> (fully migrated)migrate-mstest-v3-to-v4Check package versions before any edit. If all MSTest references are already 3.x,
no v1/v2-to-v3 error is reported, and no .testsettings or <LegacySettings>
remains, state that migration is complete and make no changes. A 3.x package
version alone does not end the migration -- leftover v1/v2-era settings files or
breaking-change errors are still in scope. Do not consolidate working v3 packages
into the metapackage. Run the existing tests only if verification was requested.
This overrides all steps below.
| Input | Required | Description |
|---|
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.