This is a mismatch between assemblies: a DLL referenced from an assembly doesn’t have a method signature that’s expected. Clean the solution, rebuild everything, and try again. Also, be careful if this is a reference to something that’s in the GAC; it could be that something somewhere is pointing to an incorrect version. Make sure … Read more
Generally, unit testing addresses a class’s public interface, on the theory that the implementation is immaterial, so long as the results are correct from the client’s point of view. So, NUnit does not provide any mechanism for testing non-public members.
If I remember correctly, “*chrome” is used to launch a special mode of Firefox (a mode in which your application has more privilegies — with less security restrictions) ; so, the fact that it’s Firefox that is launched, and not Google Chrome, is normal. If you want to launch Google Chrome, you will have to … Read more
You’ve got two different Board instances, so your call to Assert.AreEqual will fail. Even if their entire contents appear to be the same, you’re comparing references, not the underlying values. You have to specify what makes two Board instances equal. You can do it in your test: Assert.AreEqual(expected.Rows.Count, actual.Rows.Count); Assert.AreEqual(expected.Rows[0].Cells[0], actual.Rows[0].Cells[0]); // Lots more tests … Read more
For those using MSTest2, DataRow + DataTestMethod are available to do exactly this: [DataRow(Enum.Item1, “Name1”, 123)] [DataRow(Enum.Item2, “Name2”, 123)] [DataRow(Enum.Item3, “Name3”, 456)] [DataTestMethod] public void FooTest(EnumType item, string name, string number) { var response = ExecuteYourCode(item, name, number); Assert.AreEqual(item, response.item); } More about it here
As promised here’s my own solution for my problem 🙂 I hope it can help other people too! EDIT Sounds like you’d have to write a MonoDevelop add-in that serves up an API for remote NUnit runners to send data to. Not really a trivial task. The original Touch.Unit was updated to include support for … Read more
The quick answer is that you should never, ever access non-public members from your unit tests. It totally defies the purpose of having a test suite, since it locks you into internal implementation details that you may not want to keep that way. The longer answer relates to what to do then? In this case, … Read more
Microsoft recently announced “MSTest V2” (see blog-article). This allows you to consistently (desktop, UWP, …) use the DataRow-attribute! [TestClass] public class StringFormatUtilsTest { [DataTestMethod] [DataRow(“tttt”, “”)] [DataRow(“”, “”)] [DataRow(“t3a4b5”, “345”)] [DataRow(“3&5*”, “35”)] [DataRow(“123”, “123”)] public void StripNonNumeric(string before, string expected) { string actual = FormatUtils.StripNonNumeric(before); Assert.AreEqual(expected, actual); } } Again, Visual Studio Express’ Test Explorer … Read more
You need to provide a SynchronizationContext. This is how I handle it: [SetUp] public void TestSetUp() { SynchronizationContext.SetSynchronizationContext(new SynchronizationContext()); }
Daok named all the pro’s of Visual Studio 2008 test projects. Here are the pro’s of NUnit. NUnit has a mocking framework. NUnit can be run outside of the IDE. This can be useful if you want to run tests on a non-Microsoft build server, like CruiseControl.NET. NUnit has more versions coming out than visual studio. You … Read more