The benefits and challenges of executable acceptance testing

Authors:
Shelly S. Park;Frank Maurer
Affiliations:
University of Calgary, Calgary, AB, Canada;University of Calgary, Calgary, AB, Canada
Venue:
Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral
Year:
2008

Citing 10
Cited 2

A spiral model of software development and enhancement

ACM SIGSOFT Software Engineering Notes
Software requirements: objects, functions, and states

Software requirements: objects, functions, and states
The changing roles of the systems analyst

Information Resources Management Journal
Computer related risks

Computer related risks
Software Engineering Economics

Software Engineering Economics
Software Challenges

Computer
Student Experiences with Executable Acceptance Testing

ADC '05 Proceedings of the Agile Development Conference
On Formalism in Specifications

IEEE Software
Tests and Requirements, Requirements and Tests: A Möbius Strip

IEEE Software
Empirical analyses of executable acceptance test driven development

Empirical analyses of executable acceptance test driven development

Behaviour-Driven Development of Foundational UML Components

Electronic Notes in Theoretical Computer Science (ENTCS)
Linking feature models to code artifacts using executable acceptance tests

SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper, we argue that executable acceptance test driven development (EATDD) allows tighter integration between the software requirements and the implementation. We argue that EATDD improves communication between all project stakeholders. We give an overview of why previous approaches to requirements specifications are less than impressive and how executable acceptance tests help fix problems. In addition, we argue for multi-modal executable acceptance tests and how it can help improve the requirements specification. We provide some of the immediate research questions that need to be addressed in order to push forward more wide-spread use of executable acceptance test driven development.