Abstract
Test-Driven Development (TDD) is a practice that can be applied in almost all software development projects. It is a great tool to write working code and end up with clean designs. When writing code we make choices about the technologies we use and the underlying architecture. Sometimes the consequences of unfortunate choices do not show up for a while. TDD does not prevent us from making big mistakes. This paper is about such an unfortunate choice, the process of writing code based on this choice and the result. Finally, we discuss the lessons learned that can help us to avoid making big mistakes or to get a quick indication of such a mistake.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsReferences
Beck, K.: Test-Driven Development by Example. Addison-Wesley, Reading (2003)
Beck, K.: Extreme Programming Explained: embrace change. Addison-Wesley, Reading (1999)
Mar, K., Schwaber, K.: Scrum with XP. Prentice Hall, Englewood Cliffs (2002)
Cohn, M.: User Stories Applied for Agile Software Development. Addison-Wesley, Reading (2004)
Hill, M.: Testing and Refactoring Workshop, Industrial Logic
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2007 Springer Berlin Heidelberg
About this paper
Cite this paper
van Dijk, I., Wijnands, R. (2007). Test Driving the Wrong Car. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2007. Lecture Notes in Computer Science, vol 4536. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-73101-6_47
Download citation
DOI: https://doi.org/10.1007/978-3-540-73101-6_47
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-73100-9
Online ISBN: 978-3-540-73101-6
eBook Packages: Computer ScienceComputer Science (R0)