Changes since deriving from XBehave.net

Most notably

• Allowed for Background methods to be defined in multiple base intermadiate classes. Moreover, xWellBehaved.net ensure that these methods are invoked in class hierarchy order.
  • As an interesting side effect, we think that multiple Background methods may also be defined in the same class. We think that any instance of this happening ought to be rare, if ever, and that if it can be avoided, do so. Otherwise, we strongly suggest that the scope of these methods be mutually exclusive so that their order does not adversely impact either of their outcomes.
• xWellBehaved.net v2.5+ introduced the notion of TearDown methods, converse to the Background methods.
  • Also with the same caveats concerning multiple same class TearDown methods.
  • While we were there introducing TearDown methods, we decided to rename the extensions formerly known as .Teardown(...), rather as, .Rollback(...), which we think better captures the intent, but also to avoid potentially confusing overlapping verbiage.