As [ClassInitialize] is only called at the beginning, the test name is TestMethod1. This is stale after the first test run. TestContext is set for every method, and thus has the current test name. Yes, it is a bit silly.
I finally figured out the problem. In Options under Test Tools -> Test Project, there is an option “Disable background discovery of test methods”. It was turned on – I do not know how that happened, but removing the checkmark and restarting Visual Studio solved the problem.
For me, the error went away when I closed Visual Studio and opened the solution again
[TestInitialize()] is what you need. private string dir; [TestInitialize()] public void Startup() { dir = Path.GetTempFileName(); MakeDirectory(ssDir); } [TestCleanup()] public void Cleanup() { ss = null; Directory.SetCurrentDirectory(Path.GetTempPath()); setAttributesNormal(new DirectoryInfo(ssDir)); Directory.Delete(ssDir, true); } [TestMethod] public void TestAddFile() { File.WriteAllText(dir + “a”, “This is a file”); ss.AddFile(“a”); … } [TestMethod] public void TestAddFolder() { ss.CreateFolder(“a/”); … } … Read more
What worked for me: Delete folders inside .vs folder. But you still can’t delete that folder ? Probably because of Live Unit Testing, testhost.exe or testhost.x86.exe process is the cause.
To be able to set the [TestCategory] attribute at the class level, install the “MSTest V2” TestFramework using NuGet. Ref: https://blogs.msdn.microsoft.com/devops/2016/06/17/taking-the-mstest-framework-forward-with-mstest-v2/
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.
Change the call to the following Assert.IsInstanceOfType(0, typeof(int)); The first parameter is the object being tested, not the type of the object being tested. by passing 0.GetType(), you were saying is “RunTimeType” an instance of System.int which is false. Under the covers thes call just resolves to if (typeof(int).IsInstanceOfType(0))
I’m using both MSTest and NUnit at the moment. IMHO NUnit is still a better solution. If you have Visual Studio 2012 Premium edition then it’s actually quite nice, except for the fact that you can’t seem to group together tests. I like the fact it’s integrated into Visual Studio, but the lack of grouping … Read more
You should not skip test this way. Better do one of following things: mark test as ignored via [Ignore] attribute throw NotImplementedException from your test write Assert.Fail() (otherwise you can forget to complete this test) remove this test Also keep in mind, that your tests should not contain conditional logic. Instead you should create two … Read more