in

 

Browse by Tags

  • Arrange Act Assert and BDD specifications

    With Rhino Mocks 3.5 just around the corner, I've started using it to create much more readable tests. One of the things that always bothered me with Expect.Call, constraints and the like was that it mixed in the Arrange with Assert. For those that haven't heard of AAA, it's a pattern for...
    Posted to Jimmy Bogard (Weblog) by bogardj on 07-24-2008
  • Separation of Concerns by example: Part 4

    In the last part, we finally broke out the caching and data access concerns from our original class. The series so far includes: Separation of Concerns - how not to do it Separation of Concerns by example: Part 1 - Refactoring away from static class Separation of Concerns by example: Part 2 - Specialized...
    Posted to Jimmy Bogard (Weblog) by bogardj on 07-10-2008
  • 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 understand how a class worked, you simply needed to...
    Posted to Jimmy Bogard (Weblog) by bogardj on 02-16-2008
  • Converting tests to specs is a bad idea

    When I first started experimenting with BDD , all the talk about the shift in language led me to believe that to "do BDD" all I needed to do was to change my "Asserts" to some "Shoulds". At the root, it looked like all I was really doing was changing the order of my "expected"...
    Posted to Jimmy Bogard (Weblog) by bogardj on 01-10-2008
Page 1 of 1 (4 items)
Copyright Los Techies 2007. All rights reserved.
Powered by Community Server (Commercial Edition), by Telligent Systems