Release Notes

Version 5.4

These are the release notes for Release 5.4.


Typemock Intellitest	Intellitest auto completes and generates code declaration for you. Specifically, when you use an argument, it generates the Isolate.Fake.Instance for you. If the method has different overloads, it gives you all the options you need. You will receive suggestions for faking argument values (concrete, abstract classes and interfaces) for method and constructor calls.
Intellitest Behavior Wizard	Intellitest now identifies fake objects in your test and provides suggestions for controlling their behavior.
Intellitest Extensibility	Added a layer for extending Intellitest and providing your own suggestions.
General fixes	In 5.4.5 Major improvements to fake object creation and recursive fake performance Improved verification messages when verifying exact arguments, and two objects do not match Natural Mocks auto-field mocking was not being properly reset Intellitest suggestion extensibility now provides an event when a suggestion is about to be executed PartCover 2.3.0 code coverage is now supported by Isolator In 5.4.4: Major improvements to Intellitest loading time and memory consumption Fixed bug with the productivity add-in causing Visual Studio packages loading issues in some cases Fixed Intellitest conflict with VB.NET Intellitest no longer hides Intellisense when showing suggestions Fixed issues with event invocation not working properly on events defined in abstracts/interfaces Fixed compatibility problem with PostSharp Typemock MSBuild/NAnt tasks did not restore .NET version properly In 5.4.3: Improved Intellitest performance: Visual Studio no longer waits for Intellitest to finish loading Fixed an issue with Intellitest not generating completion suggestions for files in project folders Better error messages when nesting calls inside Verify Fixed a bug with True Properties that caused rare test failures Solved a few bugs with resolving methods on classes with type constraints Verify.WasCalledWithExcatArguments() provides better error message when Equals() is not implemented in the originating argument type You can use Isolate.Invoke.Event() from inside a DoInstead() delegate In 5.4.2: Fixed an issue verifying properties that have a setter with no getter Fixed a bug with event invocation - used to fail invocation if the event had a private subscriber Improved Isolate.Verify error messages - when exact matching fails for a string value, the exact location of the string difference is displayed

Known Issues	Isolator AAA does not support nested chains in WhenCalled(): Isolate.WhenCalled(() => fake.Call(fake.Do())).WillReturn(0); // not supported // instead extract the inner chain to a variable: var innerChain = fake.Do(); Isolate.WhenCalled(() => fake.Call(innerChain)).WillReturn(0); // supported In some cases Intellitest may interfere with Visual Studio Intellisense operation

Breaking changes	Removed the long-obsolete Isolate.SwapNextInstance()