I had a similar issue (with the additional message The “BuildShadowTask” task failed unexpectedly) with a project originally developed with VS2010, and got to spend the last few hours learning about yet another legacy facet of the build process. There is a good chance that you are dealing with private accessor files (.accessor), which were … Read more
I just banged my head against this one for an hour. The problem was that I had a command line project named Something.exe, which was using a class library project named Something.dll.
The first example will fail if the types are not exactly the same while the second will only fail if myObject is not assignable to the given type e.g. public class MySubObject : MyObject { … } var obj = new MySubObject(); Assert.AreEqual(obj.GetType(), typeof(MyObject)); //fails Assert.IsInstanceOfType(obj, typeof(MyObject)); //passes
TL;DR If you don’t want to read the entire article provided by Youssef and want a quick solution to how to make ModelState.IsValid return false. Do this. [TestMethod] public void TestLogin_InvalidModel() { AccountController controller = CreateAccountController(); // new code added –> controller.ModelState.AddModelError(“fakeError”, “fakeError”); // end of new code … var response = controller.PostLogin(new LoginModel() { … Read more
Unit-Test project fails to build after installing .NET 4.5
The trick is to make these methods public: [TestInitialize()] public void Setup() { _factory = new Factory(); _factory.Start(); } When they are private they do not execute.
For those that use Resharper with this issue, I discovered the fix (no need to disable Resharper): Go to Visual Studio top menu -> Resharper -> Options Find the Tools section, expand “Unit Testing” Click on “MsTest”. The checkbox should be on enabled, but the Test Settings file path below that may be blank. If … Read more
On Visual Studio 2013 I found that after setting “Default Process Architecture” to X64 I’ll go and open “Options…” and close it with “OK”, then the “Default Process Architecture” will preserved, at least for this one solution.
When declaring ClassInitialize attribute on a method, the method has to be static, public, void and should take a single parameter of type TestContext. If you’re having also other method with the AssemblyInitialize attribute on the same unit test, the test will run but will skip on all test methods and will go directly to … Read more
Another one for the googlers – this one turned out to be my problem, and it’s embarrassingly boneheaded of me. Make sure that your test project is set to build in whatever solution configuration you’re using. If the test assembly isn’t being built, VS won’t be able to find any tests in the non-existent assembly, … Read more