Comments on: Tests as todos

By: Noel

Noel — Mon, 10 Nov 2008 14:42:23 +0000

Jacob: what you do might be called functional tests
depending on the level at which you write tests. I find it
quite difficult to code all my tests at the start of
development. I usually do just a few and code up the rest
as development proceeds.

Luis: interesting article. Thanks.

By: Luis Sergio Oliveira

Luis Sergio Oliveira — Sun, 09 Nov 2008 20:42:05 +0000

I used this style sometimes and it worked very well, even if you're simply interrupting for the weekend. I've heard first about this technique from "Uncle Bob" (http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd).

By: Jacob

Jacob — Thu, 06 Nov 2008 10:01:08 +0000

Hi,

I use automated tests in a similar todo way.

We use Use Cases to drive our development. When I start out coding a Use Case, I first sit down and figure out what functionality the case covers - and then express this in a set of automated tests, as close to the use case functionality as possible (I guess this is called regression tests?).

Then I start coding the functionality making the first test case run, and basically work my way down the list of test cases, making each run. This way I am always sure of not breaking existing user functionality, and I have a good indication of when I am done. Should I find something that is not yet covered by my test cases, I write a test case for it right away, and continue working on the code.

I have been pretty successful using this method to implement complex use cases. And I have a confident feeling in my stomach once I am done, plus it makes it easier for other programmers to understand the code and make changes to it.

Best regards, Jacob