ShreyasRmsft commented the following on GitHub: Hi @cactuaroid DataTestMethod is not needed. Go ahead and use TestMethod with DataRows to data drive your tests. For any more doubts follow the official docs at https://github.com/microsoft/testfx-docs https://github.com/microsoft/testfx/issues/614 https://github.com/microsoft/testfx-docs/issues/64 So, according to Microsoft, it is preferred to use TestMethod over DataTestMethod.
You are absolutely right. Unless you provide something like an IEqualityComparer<MyPerson> or implement MyPerson.Equals(), the two MyPerson objects will be compared with object.Equals, just like any other object. Since the objects are different, the Assert will fail.
You could use the Traits feature in mstest to accomplish this. Take a look at this blog post: https://devblogs.microsoft.com/devops/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1using-traits-in-the-unit-test-explorer/
Here is a simple example using TestInitialize and TestCleanup. [TestClass] public class UnitTest1 { private NorthwindEntities context; [TestInitialize] public void TestInitialize() { this.context = new NorthwindEntities(); } [TestMethod] public void TestMethod1() { Assert.AreEqual(92, this.context.Customers.Count()); } [TestCleanup] public void TestCleanup() { this.context.Dispose(); } }
I came here searching for the solution for a similar problem. Posting this answer just in case the solution I found helps someone else. This solved it for me in Visual Studio (2012): Add New Item -> Test Settings Change the testsetting By default this is set to “Force test to run in 32 bit … Read more
No, the closest you will get is with the [Ignore] attribute. However, MSTest offers other ways of disabling or enabling tests using Test Lists. Whether you like them or not, Test Lists are the recommended way to select tests in MSTest.
I didn’t find the answer, so this is what I ended up doing. I created PrivateObjects for each level of the class’s hierarchy, and I just need to be careful when writing test cases that I use the proper one. public class BaseClass { private int one = 1; } public class SubClass : BaseClass … Read more
Kateroh, My setup looks like this (I’m using msbuild from a TFSbuild.proj): Build sln Copy all from output to %TEMP% (black magic :D) Don’t know why but mstest is looking for references in %TEMP%. Run mstest with parms: “C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe” /nologo /testcontainer:$(TestDir)\mylib.dll /resultsfile:$(TestResultFile) /runconfig:$(SlnDir)\AutomaticBuildTest.testrunconfig /searchpathroot:$(TestDir) /publish:mytfsserver /publishbuild:$(BuildDefinition) /flavor:Debug /platform:AnyCPU /teamproject:mytfsproject where AutomaticBuildTest.testrunconfig … Read more
You can use CollectionAssert with generic collections. The trick is to understand that the CollectionAssert methods operate on ICollection, and although few generic collection interfaces implement ICollection, List<T> does. Thus, you can get around this limitation by using the ToList extension method: IEnumerable<Foo> expected = //… IEnumerable<Foo> actual = //… CollectionAssert.AreEqual(expected.ToList(), actual.ToList()); That said, I … Read more
So Visual Studio uses a framework called Visual Studio Test Platform to load test adapters, https://github.com/Microsoft/vstest To discover or execute test cases, VSTest would call the test adapters based on your project configuration. (That’s why NUnit/xUnit/MSTest all ask you to install a test adapter NuGet package to your unit testing projects). So MSTest.TestAdapter exists for … Read more