How to make ANY code in ANY system unit-test-friendly

Posted by: Rico Marianis Performance Tidbits, on 20 Nov 2014 | View original | Bookmarked: 0 time(s)

There are lots of pieces of code that are embedded in places that make it very hard to test.  Sometimes these bits are essential to the correct operation of your program and could have complex state machines, timeout conditions, error modes, and who knows what else.  However, unfortunately, they are used in some subtle context such as a complex UI, an asynchronous callback, or other complex system.  This makes it very hard to test them because you might have to induce the appropriate...

Category: Refactor | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 536 | Hits: 20

Similar Posts

  • Podcast #1 – interview with Ben Scheirman co-author of ASP.NET MVC in Action more
  • Ambiguous References in DefaultWsdlHelpGenerator.aspx more
  • Spec Explorer: A Model-Based Testing tool more
  • My History of Visual Studio (Part 7) more
  • Using VSTS to Quickly Test Scenarios with Add-In Applications more
  • Dovetail is Hiring a Junior-to-Mid-level .NET Developer more
  • Unit Testing - Do Repeat Yourself more
  • How to retire (respectfully) legacy systems more
  • SimplePatch My Patching Tool more
  • CodeRush: Unit Test Runner Preview 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