
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.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 1 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
