Comments on The Typemock Insider Blog: Typemock Isolator 5.1 Released!

You need to put the Fake.Static.Constructor in the...

2008-10-16T10:45:14.957+02:00

You need to put the Fake.Static.Constructor in the [ClassInitialize] method, that is called only once.

If you have tests that need the static constructor and tests that don't, you need to separate them into different test projects. That's because you cannot control when the cctor is invoked, and it only gets called once. That's the only way to make sure that the the right tests invoke it correctly.

I'm using MSTest and I've created two tests that b...

2008-10-07T15:26:38.696+02:00

I'm using MSTest and I've created two tests that both isolate the static constructor.
Isolate.Fake.StaticConstructor [MyContext]();

Running both tests in the same run generates an error. In my current tests, this would normally be part of the test setup and not be an issue.
Is there a way to unfake it or to detect that it is already faked?

Let me know how it turned out!

2008-10-01T11:08:22.631+03:00

Let me know how it turned out!

Great! Can't wait to install it.I am not sure whet...

2008-09-30T04:26:24.618+03:00

Great! Can't wait to install it.

I am not sure whether mix parameter verification and event verification is supported in 5.1. That would be tremendously useful.