> what "red/green" means: the red phase watches the tests fail, then the green phase confirms that they now pass.
> Every good model understands "red/green TDD" as a shorthand for the much longer "use test driven development, write the tests first, confirm that the tests fail before you implement the change that gets them to pass".
From your link:
> what "red/green" means: the red phase watches the tests fail, then the green phase confirms that they now pass.
> Every good model understands "red/green TDD" as a shorthand for the much longer "use test driven development, write the tests first, confirm that the tests fail before you implement the change that gets them to pass".