On Writing Unit Tests for C#

Posted by: Simple Talk, on 08 Mar 2012 | View original | Bookmarked: 0 time(s)

Is it realistic to keep to principles of 'Test-First' and 100% coverage for unit tests when in the heat of developing commercial C# applications? Does rigorous unit-testing lead naturally to good design by enforcing testability, low coupling and high cohesion? Patrick Smacchia gives his opinion based on hard-won experience....

Category: C# | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 663 | Hits: 88

Similar Posts

  • XNA and Unity3D developers unite! UnityXNA more
  • The Full StackAccidentally Pair Programming and Writing Unit Tests more
  • Podcast #1 – interview with Ben Scheirman co-author of ASP.NET MVC in Action more
  • Avoid Entrenched Dependencies more
  • Successive Method Calls With MoQ more
  • Using VSTS to Quickly Test Scenarios with Add-In Applications more
  • Unit Testing - Do Repeat Yourself more
  • How to get started with Lucene.net more
  • IDCC conference in Israel – Spet. 14th more
  • Resource Files and ASP.NET MVC Projects 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