Ted Neward’s 2006 essay “The Vietnam of Computer Science” famously compares Object/Relational mapping to the Vietnam War: “The United States began a military project with simple yet unclear and conflicting goals, and quickly became enmeshed in a quagmire that … brought down two governments”. The analogy can equally apply to Automated Acceptance Testing: early successes lead to committing to use Cucumber Tests for all stories; more and more resources get spent covering difficult cases and maintaining fragile tests; before you know it your project is bogged down, and you are scrambling for the last helicopter off the embassy roof. This video present on the goals of acceptance testing, when and how to use them and, as importantly, when not to use them.<embed src=’http://confreaks.net/media/player.swf’ height=’270′ width=’480′ allowscriptaccess=’always’ allowfullscreen=’true’ flashvars=”&file=http%3A%2F%2Fconfreaks.net%2Fsystem%2Fassets%2Fdatas%2F988%2Foriginal%2F458-rubyconf2010-automated-acceptance-testing-the-vietnam-of-test-driven-development-small.mp4&image=http%3A%2F%2Fconfreaks.net%2Fsystem%2Fvideos%2Fimages%2F458%2Fpreview%2Fvlcsnap-2011-02-23-01h14m55s231.png%3F1298452532&plugins=viral-2&viral.allowmenu=true”/>
Video Producer: <a href=”http://rubyconf.org/”>RubyConf/</a>