mstest

I have a unit test for a method which gets an object from a collection. This keeps failing and I cannot see why, so I have created a very simple test below to create 2 supplier object and test they are equal to see if I can spot the problem in my test of my code. But this test again is failing. Can anyone see or explain why? [TestMethod()] public void GetSupplierTest2() { Supplier expected = new Supplier(); expected.SupplierID = 32532; expected.SupplierName = "Test 1" Supplier actual = new Supplier(); actual.SupplierID = 32532; actual.SupplierName = "Test 1" Assert.AreEqual(expected, actual);

When I analyse code coverage in Visual Studio 2012, any of the await lines in async methods are showing as not covered even though they are obviously executing since my tests are passing. The code coverage report says that the uncovered method is MoveNext , which is not present in my code (perhaps it's compiler-generated). Is there a way to fix code coverage reporting for async methods? Note : I just ran coverage using NCover, and the coverage numbers make a lot more sense using that tool. As a workaround for now, I'll be switching to that. This can happen most commonly if the operation you're

I have a class in my code that I don't want showing up in code coverage numbers. I added the [ExcludeFromCodeCoverage] attribute to the class definition like this: [ExcludeFromCodeCoverage] public class MyClass { ... } According to the docs ( http://msdn.microsoft.com/en-us/library/system.diagnostics.codeanalysis.excludefromcodecoverageattribute.aspx ) this should be all I need, but the class still shows up in code coverage analysis. I'm using VS2012/.NET 4.5 if that matters. Any ideas why this wouldn't work? Here's what was going on, and here's how I fixed it. I was using a .runsettings file

I am working on Unit Testing for my current project and came across something odd. The .Net UnitTesting library has both Assert.Equals and Assert.AreEqual. The remarks for Assert.Equals say to use Assert.AreEqual to compare two objects, but gives no reason as to why to do so over Assert.Equals. Can somebody explain when you should use Assert.Equals in unit testing, if ever and the difference between Assert.Equals and Assert.AreEqual? Assert.Equals is just the Equals method inherited from object . It has nothing to do with unit testing, and in fact, has no use. To be more precise, Assert.Equals

If you want to configure your VS "Load Tests" to write the results to a database server, you use the following instructions . If you want to run your "Load Tests" through powershell on a separate machine( think TFS 2018 release step ), you use the following instructions . I would like to do both, on multiple machines, in a automated manner, but there's not a great deal of documentation on this, I can run my tests like this: .\mstest /testcontainer:"C:\XXX\ABC.loadtest" But the results are kicked out to a "TRX" file rather than being placed into a database( there is some discussion on this ).