NOlbert

@saiparth Support for ordered tests in the future seems to be unlikely (see https://github.com/microsoft/testfx/issues/25#issuecomment-790955113). We fixed our (few) tests which really require ordering by merging them into a single test...

LegacySettingsd arent supported in MSTestV2.. https://github.com/Microsoft/testfx/issues/557#issuecomment-460155882 Maybe checkout the *DeployTestSourceDependencies*-Attribute or use plain DeploymentItem-Attributes. I stumbled accross this myself a year ago. The documentation is very poor here.

@vagisha-nidhi sorry for the inconvenience. I attached a demo project where the beahviour can be reproduced. [UnitTestProject1.zip](https://github.com/microsoft/testfx/files/3551082/UnitTestProject1.zip) Anyways this bug seems pretty clear as the deployment operations are done a...

One more note: The hotfix only works if you choose "Run all" within the Visual Studio Test Explorer Window. If you run a single unit test ("Run Selected Tests") the...

@vagisha-nidhi Basically the idea was to get a low-impact workaround while migrating from MSTestV1 to MSTestV2. In MSTestV1 we had a .testsettings file which used LegacySettings` ` to deploy some...

@Evangelink Since you were interested in this issue and seem make a roadmap for MSTest v3 and v4.... are there any plans to fix the main reason for this request...

While not equivalent to ordered tests it seems that at least an alphanumerical execution order is defined behaviour according to [docs](https://docs.microsoft.com/en-us/dotnet/core/testing/order-unit-tests?pivots=mstest) and [samples](https://github.com/dotnet/samples/blob/master/csharp/unit-testing/MSTest.Project/ByAlphabeticalOrder.cs)

@Evangelink Due to the conversation in #821 maybe this issue should be reopened

It works if you do it like that: ``` [TestMethod] public async Task TestFoo() { var something = new Foo(); var fullName1 = Snapshot.FullName(new SnapshotNameExtension("GetFoo")); something.GetFoo().MatchSnapshot(fullName1); var fullName2 = Snapshot.FullName(new...

One valid use case for this might be executing tests against multiple endpoints or in different environments (like Sql Server and MongoDB) for quick A/B testing, like so ``` [AttributeUsage(AttributeTargets.Method)]...