Identification and correction of besouro's faults: impact on test‐driven development experiments

Context. This thesis is framed in experimental software engineering. More concretely, it addresses the problems arisen when assessing process conformance in test-driven development experiments conducted by UPM's Experimental Software Engineering group. Process conformance was studied using the Eclipse's plug-in tool Besouro. It has been observed that Besouro does not work correctly in some circumstances. It creates doubts about the correction of the existing experimental data which render it useless. Aim. The main objective of this work is the identification and correction of Besouro's faults. A secondary goal is fixing the datasets already obtained in past experiments to the maximum possible extent. This way, existing experimental results could be used with confidence. Method. (1) Testing Besouro using different sequences of events (creation methods, assertions etc..) to identify the underlying faults. (2) Fix the code and (3) fix the datasets using code specially created for this purpose. Results. (1) We confirmed the existence of several fault in Besouro's code that affected to Test-First and Test-Last episode identification. These faults caused the incorrect identification of 20% of episodes. (2) We were able to fix Besouro's code. (3) The correction of existing datasets was possible, subjected to some restrictions (such us the impossibility of tracing code size increase to programming time. Conclusion. The results of past experiments dependent upon Besouro's data could no be trustable. We have the suspicion that more faults remain in Besouro's code, whose identification requires further analysis

Empirische Untersuchung der agilen Softwareentwicklung

Die Entwicklungsmethoden der Paarprogrammierung und der testgetriebenen Entwicklung gerieten bereits 1990er Jahren in den Fokus der Forschung. Dennoch sind zu diesen beiden Entwicklungsmethoden längst nicht alle Fragen beantwortet. In dieser Arbeit werden drei noch zu beantwortende Fragen bezüglich dieser Entwicklungsmethoden identifiziert und es wird mit drei entsprechenden Studien versucht, diese Fragen zu beantworten

Automated Recognition of Test-Driven Development with Zorro

Zorro is a system designed to automatically deter-mine whether a developer is complying with an oper-ational definition of Test-Driven Development (TDD) practices. Automated recognition of TDD can bene-fit the software development community in a variety of ways, from inquiry into the “true nature ” of TDD, to pedagogical aids to support the practice of test-driven development, to support for more rigorous empirical studies on the effectiveness of TDD in both labora-tory and real world settings. This paper introduces the Zorro system, its operational definition of TDD, the analyses made possible by Zorro, and our ongoing efforts to validate the system.

Automated Recognition of Test-Driven Development with Zorro

Zorro is a system designed to automatically determine whether a developer is complying with an operational definition of Test-Driven Development (TDD) practices. Automated recognition of TDD can benefit the software development community in a variety of ways, from inquiry into the “true nature ” of TDD, to pedagogical aids to support the practice of test-driven development, to support for more rigorous empirical studies on the effectiveness of TDD in both laboratory and real world settings. This paper introduces the Zorro system, its operational definition of TDD, the analyses made possible by Zorro, and our ongoing efforts to validate the system.