1. 20 October 2005

    1177 days ago

    A New Look at Test Driven Development

    Behavior driven development:

    It

    via Kjell Olsen1177 days ago

  2. 02 May 2005

    1347 days ago

    Mike Clark's Weblog

    Learning ruby through testing it feature by feature – nice idea. Not only do you have a quick reference of everything you’ve ever learned, but if something in the library changes, you’ll know about it quickly.

    We have no idea if Ruby did what it should have done: we just know what it did. That is, we used the language as a tool to explore itself. In the same way that a test is better than a specification, the language is better than a description of the language. The test is definitive—when we ask Ruby what the answer to ‘Hello! ’ * 3 is, we’re going to the horse’s mouth. It doesn’t matter what the documentation says; what we’re testing is what actually happens. And that’s learning. So the test is both a learning test and a regression test.

    via Kjell Olsen1347 days ago

  3. 29 March 2005

    Test-Driven Development

    Kent Beck

    1382 days ago

    A real clear look at what TDD is, and how to go about using it in writing your own software.

  4. Also somewhat recently

      |