You could use LINQ: Assert.That(people.Any(p => p.Name == “joe”)); or, if you want to be explicit about there being exactly one person with each name: Assert.That(people.Count(p => p.Name == “joe”), Is.EqualTo(1)); If you want a better error message than “Assertion failed, expected true, was false”, you could create your own assert method. For several collection-related … Read more
Since version 2.5.7, NUnit allows Teardown to detect if last test failed. A new TestContext class allows tests to access information about themselves including the TestStauts. For more details, please refer to http://nunit.org/?p=releaseNotes&r=2.5.7 [TearDown] public void TearDown() { if (TestContext.CurrentContext.Result.Status == TestStatus.Failed) { PerformCleanUpFromTest(); } }
Such a situation normally occurs when the unit tests are using shared resources/data in some way. It can also happen if your system under test has static fields/properties which are being leveraged to compute the output on which you are asserting. It can happen if the system under test is being shared (static) dependencies.