@inbook {Simula.SE.439,
	title = {Refactoring Test Code},
	booktitle = {eXtreme Programming Perspectives},
	year = {2002},
	pages = {141-152},
	publisher = {Addison-Wesley Longman},
	organization = {Addison-Wesley Longman},
	chapter = {14},
	isbn = {978-0201770056},
	author = {van Deursen, Arie and Moonen, Leon and van den Bergh, Alex and Kok, Gerard},
	editor = {Marchesi, M. and Succi, G. and Wells, D. and Williams, L.}
}
@inproceedings {Simula.SE.525,
	title = {Refactoring Test Code},
	journal = {Proceedings 2nd International Conference on Extreme Programming and Flexible Processes in Software Engineering (XP2001)},
	year = {2001},
	month = {may},
	type = {Conference},
	abstract = {Two key aspects of extreme programming (XP) are unit testing and merciless refactoring. Given the fact that the ideal test code / production code ratio approaches 1:1, it is not surprising that unit tests are being refactored. We found that refactoring test code is different from refactoring production code in two ways: (1) there is a distinct set of bad smells involved, and (2) improving test code involves additional test-specific refactorings. To share our experiences with other XP practitioners, we describe a set of bad smells that indicate trouble in test code, and a collection of test refactorings to remove these smells.},
	author = {van Deursen, Arie and Moonen, Leon and van den Bergh, Alex and Kok, Gerard},
	editor = {Marchesi, M. and Succi, G.}
}
