Unit Test Boundaries

Posted by: youve been HAACKED, on 22 Jul 2008 | View original | Bookmarked: 0 time(s)

One principle to follow when writing a unit test is that a unit test should ideally not cross boundaries. Michael Feathers takes a harder stance in saying A test is not a unit test if: It talks to the database It communicates across the network It touches the file system It cant run at the same time as any of your other unit tests You have to do special things to your environment (such as editing config files) to run it Tests that do these things arent...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: Refactor | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 994 | Hits: 33

Similar Posts

  • Software unit testing and DB2 sql loop test code more
  • Welcome the WebUI Test Studio v2.0! more
  • Podcast #1 – interview with Ben Scheirman co-author of ASP.NET MVC in Action more
  • Testing.StackExchange – The “StackOverflow” for Software Testers more
  • Spec Explorer: A Model-Based Testing tool more
  • Continuous Integration with WebAii for Silverlight, NUnit and CruiseControl.NET more
  • VS 2010 and .NET 4.0 Beta 2 more
  • Beta Testers Wanted: DotNetNuke 5.2.0 Beta Now Available more
  • Avoid Entrenched Dependencies more
  • TestRail test management beta now available 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