chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes

I usually apply Isolated attribute on a test class level, so I don't need to remember to mark individual tests as Isolated. But when I started using new TestCase feature of NUnit 2.5 (ability to run multiple parameterized tests using single test method), I had to apply Isolated attribute to individual tests, otherwise some tests failed. It looks like it has to do with a test runner and the order of test execution - often there is no clear pattern of what makes tests fail. But there is a clear pattern of how to fix them: apply Isolated attribute to a method that uses TestCase, even though the whole test class is marked as Isolated.

To me it looks like a bug in TypeMock Isolator related to isolation of test cases - expectations on them are not properly cleared when multiple test cases are invoked from a single method with a help of TestCase attribute.
asked by vagif (19.4k points)

2 Answers

0 votes
Hi Vagif,

Indeed it's a bug :evil:
We'll update you once it is fixed.
answered by ohad (35.4k points)
0 votes
Hi Ohad,

This error seems to have been fixed. I've checked tests with TestCase attribute. They work now.
answered by vagif (19.4k points)