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

On Thu, Nov 21, 2019 at 3:34 PM Chris Riesbeck <[email protected]>
wrote:


> I prefer "test-driven" over "test-first". Tests define what needs to be
> accomplished, in tiny slices, in some executable "clear when it's done"
> form. There's TDD with unit tests at the code task level, there's TDD
> with acceptance tests at the user story level, and there's TDD with
> business goals at the product level, e.g., reduced user error or
> increased usage of some feature.
>

I tend to delineate "-first" from "-driven" based on how one uses the
tests. When one uses feedback from the tests to change what they do next,
then the tests are "driving" something. As the programmers defers
commitment to later in the process, that programmer is using the tests to
_drive_ more. Usually this relates to refactoring and design decisions, but
I don't suppose that it has to be limited to that.

In that sense, I don't prefer test-driven over test-first as such, although
I generally have a bias towards deferring commitment, which coincidentally
aligns with -driven over -first.
-- 
J. B. (Joe) Rainsberger :: https://tdd.training :: http://www.jbrains.ca ::
http://www.thecodewhisperer.com

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

View/Reply Online (#160327): https://groups.io/g/extremeprogramming/message/160327
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]]
-=-=-=-=-=-=-=-=-=-=-=-