Your tests will be more maintainable (6 entries)

When using Isolator, setting behavior of a method once, changes that method behavior for all calls against it. That means that if your production code changes and calls a method …

With Isolator, setting the behavior of a method also sets the behavior of all its overloads by default, so if your production code changes to call a different overload of that …

With Isolator, verifying method calls is less brittle. Even if your code calls a method multiple times, you can verify that it was called at least once with the correct …

With Isolator, you can fake the behavior of all instances (existing and future instances) of a specific type, regardless of how many there will be. For example, if …

With Isolator, when faking a method’s behavior, arguments for that method are ignored by default. This is the opposite of what all other frameworks do, and there’s a simple reason …

Recursive fakes not only make tests shorter and readable. They can also make your tests more robust. Ever had a test break because you change internal implementation? That’s because …