Re: Three Law of TDD - to strictly follow, or not?

Exactly. You should only commit the test after you've gone through the full
Red-Green-Refactor. In fact, assuming you're using DVCS or your own branch,
I would go so far as to say that you should always
Red-Green-Refactor-Commit. I've written more on this here:

http://ardalis.com/rgrc-is-the-new-red-green-refactor-for-test-first-development


On Wed, Aug 27, 2014 at 4:09 AM, Samuel Åslund [email protected]
[testdrivendevelopment] <[email protected]> wrote:

>
>
> On 14/8/26 17:48, Kaleb Pederson [email protected]
> [testdrivendevelopment] wrote:
>
>
>  Do you consider, "an incomplete but green test is at best misleading and
> at worst wrong"?
>
>
> You might want to consider the difference between a test during
> development locally and a test that have been checked in to the common
> repository.
>
> I have been confused by tests with names saying they check something that
> is not checked, making me spend time searching for problem in the wrong
> place.
> On the other hand during TDD it is rather important to know that the test
> actually fails, like you and others describe. The key as I see it is if the
> test is committed or not. Mostly the tests confusing me have come from
> being interupted while they happened to be green and then missing that they
> was not compete when coming back.
>
> Regards,
> //Samuel
>
>  
>



-- 
Steve Smith
http://Ardalis.com/
http://twitter.com/ardalis