XP with acceptance-test driven development: a rewrite project for a resource optimization system

Authors:
Johan Andersson;Geoff Bache;Peter Sutton
Affiliations:
Carmen Systems AB, Odinsgatan, Göteborg, Sweden;Carmen Systems AB, Odinsgatan, Göteborg, Sweden;Carmen Systems AB, Odinsgatan, Göteborg, Sweden
Venue:
XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering
Year:
2003

Citing 2
Cited 4

Extreme programming explained: embrace change

Extreme programming explained: embrace change
Endo-testing: unit testing with mock objects

Extreme programming examined

EasyAccept: a tool to easily create, run and drive development with automated acceptance tests

Proceedings of the 2006 international workshop on Automation of software test
Teaching software development with ATDD and easyaccept

Proceedings of the 39th SIGCSE technical symposium on Computer science education
Are fit tables really talking?: a series of experiments to understand whether fit tables are useful during evolution tasks

Proceedings of the 30th international conference on Software engineering
Multithreading and web applications: further adventures in acceptance testing

XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

In his recent book "Test-Driven Development" [1], Kent Beck describes briefly the concept of "Acceptance-Test Driven Development", and is broadly sceptical to whether it will work. After a successful project that used this technique, we wish to argue in favour of it and the TextTest [7] tool that we have built up around it. We have found that a working XP process can be built based around using only automated acceptance tests, and not doing any unit testing. In this paper we explain and analyse our XP process, its strengths and limitations, and by doing so we hope to inspire others to try and make it work for their projects too.