Browse by Tags

• BDD
• Behavior-Driven Development
• Legacy Code
• MonoRail
• PabloTV
• Patterns
• Refactoring
• Testing
• Tools

• PabloTV: Eliminating static dependencies screencast

  Nature abhors a vacuum. It turns out she also abhors static dependencies (I have my sources). Static dependencies are the modern-day globals, often exposed through classes named "Helper". I've certainly been guilty of overusing static dependencies... Posted May 06 2008, 07:24 AM by bogardj with | with 11 comment(s) Filed under: Legacy Code, Refactoring, BDD, TDD, PabloTV

• Should you TDD when flying solo?

  A couple of weeks ago a question came up on the ALT.NET message board : Does TDD make sense when you're the only developer in your company? To me, this is akin to the following questions: Is quality important? Is maintainability important? Is design... Posted Apr 22 2008, 08:39 PM by bogardj with | with 13 comment(s) Filed under: TDD

• Auto-mocking container pitfalls?

  I'm taking a closer look at the auto-mocking container idea, specifically as we're including it in the upcoming release of NBehave. I'm a little wary of prolonged use, but wanted to get some feedback (it's also on the ALT.NET message board... Posted Apr 21 2008, 07:57 PM by bogardj with | with 3 comment(s) Filed under: Tools, TDD

• Review - xUnit Test Patterns

  I consider one of the measures of quality of a book to be the number of personal assumptions challenged by its material. To that point, Gerard Meszaros' xUnit Test Patterns did not disappoint. Perhaps the biggest assumption was a dogmatic view of... Posted Mar 16 2008, 10:15 PM by bogardj with | with 6 comment(s) Filed under: TDD

• Clearing up the Mock confusion

  There's some bad blood concerning Mocks, and a lot of it rightfully so. Because of popular mocking frameworks, the name "Mock" has become interchangeable for "Test Double". In Texas, we ask for a Kleenex, not a tissue, and a Coke... Posted Mar 13 2008, 09:57 PM by bogardj with | with 4 comment(s) Filed under: TDD

• Advanced mocking: mocks and stubs

  Test Spies can help us verify the indirect outputs of a system under test. If an OrderProcessor needs to send an email, we don't want that test sending real emails, so we set up a Test Spy to capture that indirect output so we can verify it inside... Posted Mar 12 2008, 10:16 PM by bogardj with | with 5 comment(s) Filed under: TDD

• The many faces of ExpectedException

  I'm not a fan of the style most xUnit frameworks suggest for verifying exceptions. After seeing the problems with using an attribute to perform assertions, many frameworks have come up with their own way of their own way of doing it. Outside using... Posted Mar 10 2008, 10:25 PM by bogardj with | with 4 comment(s) Filed under: 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

• Eliminating obscure tests

  One of the purported benefits of unit tests and TDD in general is unit tests doubling as living documentation. Unit tests are documentation in the form of executable client code demonstrating small units of behavior. The idea is that if you wanted to... Posted Feb 16 2008, 06:47 PM by bogardj with | with 2 comment(s) Filed under: BDD, Behavior-Driven Development, TDD

• Getting over the TDD hump

  Chad mentioned that the first 2 hours of TDD are the hardest . Without a good pair by your side, the pain can stretch well beyond a couple of hours. Maybe I had a rare experience, but my first experience with TDD was successful and had very few bumps... Posted Feb 13 2008, 08:31 PM by bogardj with | with 4 comment(s) Filed under: TDD