We use this attribute all over the place and we clearly misunderstood the second parameter (shame on us). However, we definitely have used it to check the exception message. The following was what we used with hints from this page. It doesn’t handle globalization, or inherited exception types, but it does what we need. Again, … Read more
I’ve looked at one such project where the number of unit tests made the system take too long to test everything. “Too long” meaning that you basically didn’t do that as part of your normal development routine. However, what they had done was to categorize the unit tests into two parts. Critical tests, and “everything … Read more
The answer, at least so far, is to install the R# 2017.2 EAP 13 … Yes, the 13, not the 12
I solved this problem with locking: public static class IntegrationTestsSynchronization { public static readonly object LockObject = new object(); } [TestClass] public class ATestCaseClass { [TestInitialize] public void TestInitialize() { Monitor.Enter(IntegrationTestsSynchronization.LockObject); } [TestCleanup] public void TestCleanup() { Monitor.Exit(IntegrationTestsSynchronization.LockObject); } //test methods } // possibly other test cases This can of course be extracted to a … Read more
NUnit contains a [TestCase] attribute that allows implementing parametrized tests. This does not exist out of the box in MSTest – it can be done via extensibility though. MsTest’s ExpectedException attribute has a bug where the expected message is never really asserted even if it’s wrong – the test will pass. NUnit ships with an … Read more
TL;DR version: Other answers have commented on workarounds and use of the more recent Traits options. However, none quite tell you how to specifically exclude tests for a trait. To do so, simply use a – (minus) to negate a filter in the search box, e.g.: -Trait:”DatabaseIntegration” This will exclude all tests with that trait. … Read more
Found it: Assert.IsTrue(expected.SequenceEqual(actual));
After some additional poking around the UI, I figured out a decent way to do this: Open the Test Explorer window. (Test menu > Windows > Test Explorer) Click on the little down arrow just to the left of the search field. From the context menu that appears, select Project. The Test Explorer window contents … Read more
MSTest has been released as a new NuGet package solution that is no longer tightly coupled to the Visual Studio version. Your new projects are using MSTest 2.0. MSTest V2 release annoucement: https://devblogs.microsoft.com/devops/taking-the-mstest-framework-forward-with-mstest-v2/