Migrated from MSTest v1: AssemblyInitialize method has wrong signature

Description

We are trying to migrate our tests to MSTest v2. Our test assemblies use [AssemblyInitialize] and after migration all our test are failing with the following message:

Method …InitializeAssembly has wrong signature. Parameter 1 should be of type Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.

Our InitializeAssembly method looks like this:

[AssemblyInitialize]
public static void InitializeAssembly(TestContext context)
{
	// code
}

First of all, it does meet the requirements. Also, I noticed that the actual message in the current version of code looks slightly different.

This makes me think that Visual Studio somehow uses the old MSTest tooling despite the fact that our projects no longer reference Microsoft.VisualStudio.QualityTools.UnitTestFramework and reference MSTest.TestFramework and MSTest.TestAdapter instead.

Environment

We are referencing MSTest packages version 1.1.14. The problem is present both in VS 2017 test runner and ReSharper test runner.

We are also using the old .csproj format. Is it possible that we need to make some additional migration changes in our csproj files?

[AbhitejJohn]

That’s great news @ivonin .

It seems to me that .runsettings doesn’t support deployment items in any way. Is there a workaround for that?

you can use the DeploymentItemAttribute for that. Adorn this on a TestClass or TestMethod that needs the folder\file deployed.

is it possible to make things more clear when there is such misconfiguration?

We do throw out the following warning in the Output -> Tests pane when these settings are used. Warning : A testsettings file or a runsettings with a ForcedLegacyMode set to true is not supported with the MSTest V2 Adapter.

[AbhitejJohn]

Feel free to file a new issue if you run into other problems with the migration effort.