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

Hi ...

sent from iPad, probably via Mars. Errors, if any, are not mine.
[email protected] is a better address for me, maybe.

> On Nov 21, 2019, at 10:48 AM, Steve Gordon <[email protected]> wrote:
> 
> The work process is different for TDD at the unit level than at the system level (acceptance, story slice, business goal, etc.).  In TDD at the unit level, a new tests is written after each time the code satisfies the previous test (and is refactored), whereas at the system level, several tests are normally written before implementation starts and rarely are new tests added at the system level during implementation of a story.  

I would not call the thing above TDD. TDD is red/green/refactor. The thing above is more commonly called ATDD (Acceptance TDD), and I don't really like that term as much as I might have in the past. Those tests are what XP called Customer Tests and they are a different practice from Programmer Tests. 

The latter are now thought to be best done using TDD. 

It is often sensible to make ATDD tests work "one at a time" and it would not be unreasonable to enter them into the test system one at a time, which would make the process look more like test-first if not TDD.

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

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