Acceptance Test Driven Development is an extension of the idea of test-first programming to system level functionality. TDD is about writing a unit test, making it pass, and making it pretty. Acceptance TDD is about writing an acceptance test, automating it (if it wasn't written in executable form in the first place), and implementing the missing functionality highlighted by the acceptance test.
Originally posted by Lasse Koskela: Acceptance TDD is about writing an acceptance test, automating it (if it wasn't written in executable form in the first place), and implementing the missing functionality highlighted by the acceptance test.
Using TDD to implement that functionality, as far as I can tell?
So you would have an outer loop, with high level tests written from a user perspective, which drives a more tight inner loop of low level tests written from the developer's perspective, which drives the design of the production code?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Jan 23, 2002
I most certainly consider that a good practice but I would still consider it Acceptance TDD even if the code was written test-last. That's just my "definition", of course.