Sticky behavior

All behavior in Isolator++ Professional is "sticky" by default. A behavior's definition continues to be there by default, until cleared.

For example, if you've set some method's behavior, it will continue to behave that way no matter how many times it's called.

If it's supposed to return a value, it will always return that value.

When using sequences of behaviors, the last behavior set on the object remains sticky for the lifetime of the test or until ISOLATOR_CLEANUP is called.

Sticky behavior means our tests will become more robust if some internal code that we don't care about uses them more than we expected, or is refactored to use them more times, or less times. Over time there will be less breaking tests for the wrong reasons.