Abstract
Agile processes tend to minimize documentation. As the Agile Manifesto states, working software is preferred over comprehensive documentation. In the course of developing working software, tests are natural byproducts. What useful project documentation is already captured in these tests, and how do we leverage it? The concept of tests as documentation has been under-discussed in the community, and this workshop has attempted to facilitate that discussion.
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 subscriptionsAuthor information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2004 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Kohl, J., Marick, B. (2004). Agile Tests as Documentation. In: Zannier, C., Erdogmus, H., Lindstrom, L. (eds) Extreme Programming and Agile Methods - XP/Agile Universe 2004. XP/Agile Universe 2004. Lecture Notes in Computer Science, vol 3134. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-27777-4_27
Download citation
DOI: https://doi.org/10.1007/978-3-540-27777-4_27
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-22839-4
Online ISBN: 978-3-540-27777-4
eBook Packages: Springer Book Archive