With other frameworks, if, during debugging, you open the watch window, and evaluate (even by mistake) the value of a fake property of a method, the isolation framework will treat this action as if it was run from production code, and so you might fail the test or cause unknown behavior from the faked methods or properties.

Isolator is smart enough to detect such actions and will do two things:

• Return the fake value that was assigned to that method or property to see in the debugger
• Ignore this action as if it never happened so the test can continue as is even during debugging