It's what a Mocking Framework should be-
Which means you can fake more than just public virtual methods and you can reach higher test coverage in a fraction of the time.
You can fake statics, private, constructors, events, linq, ref args, live, future, static constructors. You name it.
Built for TDD, Built for Your Legacy Code
Isolator is great for TDD where you need to fake out components, and build from the ground up to test your legacy code.
The best part - no need to change your code, even legacy code.
Sleek API: Concise, Fluent and Discoverable
Isolator has well-tuned API. It's so concise you can fake entire object models with a single statement.
It's so fluent you can almost read it like English. It's so discover-able, all you need to fake is Isolate.
The API is also complete, which means that you won’t find yourself looking for ways to verify calls or handle static constructors.
Safer than Ever
Isolator is built to protect you.
The All-new Stale-Fake feature protects you from inter-test impacts.
You won’t have to search for the violating code in a haystack of tests. Fake.Dependencies automatically generates the constructors’ arguments.
Your constructors won’t require any change in your tests. WhenCalled ignores arguments by default. Your argument-values won’t require you to modify any of your tests.
600% Coverage Improvement
Our customers report, on average, 600% improvement in code coverage since using Isolator. Within 2 months.
Isolator Insight. Clearer than Ever.
For that light bulb moment. Sometimes you need to understand how your tests work. Sometimes you are simply looking for answers. Insight gives you a clear grasp of what goes on in your tests. It’s even smart enough to analyze your isolated code at runtime. The results, by the way, are brilliant.
StackOverflow Exception Protection
This is a sleek, new feature. Isolate will protect you from StackOverflow.
Which means that if your code runs in an infinite loop your runner won’t crash and the rest of your tests will run as normal.
All-new features put even more power in your hands.
* New pInvoke faking allows you to fake DLLImport methods.
* New Fake Future Interface feature will fake future instances that implement that interface.
* Use the New Invoke Private Constructor to create objects with private constructors.
* You can now validate and count the times a constructor was called.
Additional powerful features give you full control over statics, private, constructors, events, linq, ref args, live, future, static constructors. You name it (No, seriously, give it a name).
Write Great Unit Tests
Isolator's API is crafted in a way that will help you write great tests.
One aspect of this is Arrange Act Assert. This means that the different parts of testing are separated.
Using our API will keep you on the right path. Which means that you will never find an assert hidden in the arrange part of the test.
Suits Your Environment. Fits Your Code. Integrates with Virtually Everything
Isolator has been around long enough to have the deepest and widest integration. Which means that Isolator works with your Visual Studio and build server and also works with your runner and works with your code coverage tools of choice.
Visual Studio 2010, 2012, 2013, 2014, 2017 & 2019. NCover and many more.
Another brilliant feature is the Auto linker. Isolator will automatically link with your code-coverage and profiling tools. Which means that using the tools together is a simple plug-and-play.
Isolator works seamlessly with your code: ASP, ASP/MVC, SharePoint, Entity Framework, WCF, Linq, Databases, Ioc Containers and more...
Isolator is built to make debugging and fixing tests easy.
Verifications fail with Simple clear messages that guide you to the exact problem.
To make it more brilliant, we added the No Side Effect Debugging. Which means that while debugging, sequencing is not activated and you won’t need to rerun the test after property evaluation.
We even removed the Isolator methods from the stack trace, so that it’s easier for you.
Choose Your Design Restraints
You can control forcing Testable Design, or keep your design pragmatic.
Don't Believe It's the Best Tool for Unit Testing? Try It Yourself