isolator cleanup routine?

I guess I should read the docs more carefully. Is this [ClearMocks] attribute the one I want?

see here: [url]http://docs.typemock.com/Isolator/##typemock.chm/html/T_TypeMock_ClearMocksAttribute.htm[/url]

I tried the attribute both on the class and the methods and I'm still getting exceptions about the Faking.

What am I missing?

More information that may or may not be relevant.
I have 2 isolator unit test projects in this SLN & 1 regular unit test project.

when I run 1 test from the first unit test project and all from the 2nd project, I get the exception.

If I run just tests from 1 project or the other, I get no exceptions.

Hi,

ClearMocks attribute belongs to the previous Isolator API.
If you are using Arrange Act Assert API try using the [Isolated] attribute :)

Please let me know if it helps.

I'm using the isolated attribute at the class level.

i.e.

[TestClass(), Isolated]
public class ServiceTest
{

I tried adding it at the method level and I'm still getting the issue.

Any ideas?

Hi,

Can you please post here the tests code?
Also please specify which Isolator version are you using.

I don't think I can due to the NDA at my company. I'm using 6.1.2

I can probably post pseudo code, if that would be helpful.

Hi,

Sure, lets try :)

Did something happen to the forums? I remember there being more in this post. I came here to say, I tried putting the unit tests in a class and then loading that class into a unique appdomain for each unit test. It seems like it is working.

I think the issue is -- and maybe your dev team has a more elegant solution is that static constructors only get called once -- so if you fake them in 1 unit test the only way to sanitize / protect the other unit tests is to put any unit test that fake a static constructor in its own appdomain.

Is this correct?

Yes, you're correct (on both post and the static constructor). Part of the post is not here (we've upgraded the forum the last posts where not imported but I've found them in the archive).

We're working on a solution for this case, we're discussing a more general way to deal with it. We also tracked a bug related to it which we hope to fix soon.

I'll update on this post when the new solution is provided and when the bug is fixed.

Regards,
Elisha,
Typemock Support

Hi,

We fixed the bug, I sent you an email with the link to download it.
Please check it out and let me know if it solves the problem.