The Three Values of a Good Isolation Framework

Posted by: ISerializable, on 14 Oct 2012 | View original | Bookmarked: 0 time(s)

A good isolation framework(mocking framework but that is a horrible name for it. the word mock is overloaded already) should follow three values to not be a hindrance, and actually be helpful to me: Simple to use. For example, a single point of entry in the API, easy to remember API, or Intellisense guidance. Test Robustness. Making sure the test can live as long as possible while the system changes, and it only breaks when something important to it changes. Things like recursive fakes help...

Category: Agile | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 1819 | Hits: 48

Similar Posts

  • Why not Classic (Legacy) ASP? more
  • TDD Master Class Day # 3 What I learned today more
  • Enterprise Architecture Meta-model, size doesn't matter more
  • You should NOT use ASP.NET MVC if. . . more
  • Hey, nice package! more
  • Oxite - Oh Dear Lord Why?! more
  • Isolation frameworks lessons from the wild more
  • EDMX vs. EDM more
  • What Does that .NET Namespace Mean: System.* and Microsoft.* more
  • A Vertiable Cornucopia of Silverlight Toolkit Resources more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD