• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

What is "Acceptance"?

 
clojure forum advocate
Posts: 3479
Mac Objective C Clojure
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi.
I have been checking your new book page at Manning web site.
The page mentioned "Acceptance" TDD so many times.
What is Acceptance TDD? is it a fork of TDD?
Thanks.
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
try to follow this link
http://www.amazon.com/Test-Driven-Acceptance-Java-Developers/dp/1932394850
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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?
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That makes sense. Thanks!
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic