Browse by Tags

• Legacy Code
• MonoRail
• Patterns

• Quality and code coverage

  It's an age-old question: should our team's goal be 100% coverage? A valid question, but one I've never much cared about in practice. The idea is that the team, all practicing TDD, should dutifully measure and add unit tests until they reach... Posted Sep 09 2008, 07:59 AM by bogardj with | with 9 comment(s) Filed under: Testing, TDD

• Advanced mocking: anonymous test spy

  When practicing TDD, I create interfaces to abstract away the ugly stuff, like databases, file I/O, web service calls, email messages, and other external systems. I can run tests now that don't have to interact with real implementations of these external... Posted Mar 06 2008, 10:43 PM by bogardj with | with 24 comment(s) Filed under: Testing, TDD

• Advanced mocking: auto-interaction testing

  When dealing with legacy systems or those not designed with specific testability scenarios in mind, you have to test your changes in non-traditional means. In normal mocking (or test double ) scenarios, you have some kind of external dependency that you... Posted Mar 05 2008, 09:44 PM by bogardj with | with 7 comment(s) Filed under: Legacy Code, Testing, TDD

• Unit testing MonoRail controllers - Redirects

  When developing with MonoRail , one of the common operations is to redirect to other controllers and actions. Originally, I looked at the BaseControllerTester to help test, but it required a little too much knowledge of the inner workings of MonoRail... Posted Feb 18 2008, 09:40 PM by bogardj with | with 7 comment(s) Filed under: Patterns, Testing, TDD, MonoRail