Re: [extremeprogramming] The principle behind How Test-Driven Development Works

And we need to create the conditions for rapid safe refactoring because we
are quite likely not delivering the right system due to the error-prone
human nature of the all people building the system, asking for the system,
(collaterally) impacted by the system, and managing the process.

If it weren't for human nature, it would be mathematically more efficient
to just sling the right code the first time.

On Tue, Nov 19, 2019 at 12:10 PM Tim Ottinger via Groups.Io <linux_tim=
[email protected]> wrote:

> Yes, and....
>
> I always teach that the value/purpose/use of TDD is to enable quick and
> successful refactoring.
>
> The enablement is in feedback that the code still does (at least) what the
> developers think it should do.
>
> And, of course, this leads to understanding that tests which lock down the
> solution structure instead of the solution behavior are not good tests for
> TDD. They might be a good starting point (pin-down tests) but they’ll need
> to be refactored along with the code if we’re to create the conditions for
> rapid, safe refactoring.
>
> Tim
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160239): https://groups.io/g/extremeprogramming/message/160239
Mute This Topic: https://groups.io/mt/39414677/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-