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

The differences in both ownership and work process are important enough
that ATDD or executable specification or some other term would be better
than overloading TDD.

On Thu, Nov 21, 2019 at 11:42 AM Chris Riesbeck <[email protected]>
wrote:

> I didn't mean to blur TDD = test-driven development and the
> red/green/refactor process.
>
> But isn't there also TDD = test-driven design, where at the unit level,
> we design our code to be more testable, at the acceptance test level, we
> design our solution to be minimal, and at the business level we design
> our user story goals to solve real problems?
>
> --
> ................................................
> Christopher Riesbeck (he/him/his)
> Associate Professor, Computer Science
> McCormick School of Engineering, Northwestern University
> Director, MS in Computer Science
> Co-director, The Center for Computer Science and Learning Sciences
>
> Home page: https://users.cs.northwestern.edu/~riesbeck/
> Calendar: https://users.cs.northwestern.edu/~riesbeck/calendar-weekly.html
>
>
> 
>
>

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

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