Typemock Isolator pros and cons

[andreister]

Hi, please have a look at my take on pros and cons for Typemock.

Do you agree/disagree? Anything else you might consider as a pro/con?

Pros:
1. Extremely powerful. Can mock static methods, sealed and private
classes, does not need Dependency Injection to work.
2. Type safe.
3. Simple API.

Cons:
1. Not open source and some features available in paid version only.
2. Cannot mock fields.
3. Cannot mock mscorlib types.

[andreister]

(by typesafe I mean you *can* write type safe mocks - not in
Reflective Mocks though)

[Paulio]

I believe you can mock fields since v4.2

[andreister]

Opps, true.

However, with AAA this one throws System.ArgumentOutOfRangeException
in ArrangeActAssert recorder:

[Test, Isolated]
public void TestFoo()
{
var foo = Isolate.Fake.Instance<Foo>();
Isolate.WhenCalled(() => foo.Boo).WillReturn(10);

Assert.AreEqual(10, foo.Boo);
}

public class Foo
{
public int Boo;

[andreister]

It appears that AAA Isolator does *not* support mocking fields - only
properties.

[Paulio]

I don't have 4.2+ but...
http://blog.typemock.com/2008/04/mocking-fields-why-it-was-implemented.html

> > > > 3. Cannot mock mscorlib types.- Hide quoted text -
>
> - Show quoted text -

[andreister]

As per

http://www.typemock.com/community/viewtopic.php?t=1126&sid=a00ca12b36da776b35cc731e7499538a

"..Isolator AAA does not support faking fields - only properties..."

On Jan 19, 5:35 pm, Paulio <pdkm2...@hotmail.com> wrote:
> I don't have 4.2+ but...http://blog.typemock.com/2008/04/mocking-fields-why-it-was-implemente...