That was the way I was shown in tutorials I have seen regarding testing. Essentially you make everything bit sized to the point where you would write an empty method that fails you then add to it until it does not fail, you then have a method that has been engineered as little as possible to work. The theory behind this is each method only gets as much attention as it needs to work and over engineering becomes moot..

Of course this still leaves the big, show me how to test correctly, hole in my developmental efforts. I have also found lately that there is so much knowledge floating around that one of the skills a programmer needs is to sort out which is relevant and which is not. Filtration seems to be something I am slowly but surely getting better at.