Abstract
The actual and appealing objective of XP’s approach to unit testing is to improve quality by avoiding errors beforehand rather than to find and fix bugs afterwards. Conventional testing, on the contrary, focuses on a posteriori analysis to find errors and issues that should be corrected. Both approaches have their advantages and drawbacks, and both are valuable and necessary. This paper describes how we combined both approaches by extending our test management environment TEMPPO for unit testing with JUnit to include testers in early unit testing activities.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
Beck, K.: eXtreme Programming explained: Embrace Change. Addison-Wesley, 2000.
Cunningham & Cunn., Inc.: Extreme Programming Roadmap at WikiWiki. (http://c2.com/cgi/wiki?UnitInUnitTestIsntTheUnitYouAreThinkingOf)
Hofman, A.: Test Management in XP Environments with TEMPPO. Technical Report, SCCH, 2001.
JUnit.org: The JUnit Tool. http://www.junit.org
Link, J., Fröhlich, P.: Unit Tests mit Java: Der Test-First-Ansatz. dpunkt, 2002.
Moore, I.: Jester-a JUnit test tester. in Proc. XP2001, Cagliari, Italy, May 2001.
Myers, G.J.: The Art of Software Testing. Wiley, 1979.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2003 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Ramler, R., Czech, G., Schlosser, D. (2003). Unit Testing beyond a Bar in Green and Red. In: Marchesi, M., Succi, G. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2003. Lecture Notes in Computer Science, vol 2675. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-44870-5_39
Download citation
DOI: https://doi.org/10.1007/3-540-44870-5_39
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-40215-2
Online ISBN: 978-3-540-44870-9
eBook Packages: Springer Book Archive