Standard

Test-Driven Code Review: An Empirical Study. / Spadini, Davide; Palomba, Fabio; Baum, Tobias; Hanenberg, Stefan; Bruntink, Magiel; Bacchelli, Alberto.

Proceedings of the 41st ACM/IEEE International Conference on Software Engineering. 2019.

Research output: Chapter in Book/Report/Conference proceedingConference contributionScientificpeer-review

Harvard

Spadini, D, Palomba, F, Baum, T, Hanenberg, S, Bruntink, M & Bacchelli, A 2019, Test-Driven Code Review: An Empirical Study. in Proceedings of the 41st ACM/IEEE International Conference on Software Engineering. https://doi.org/10.5281/zenodo.2551217

APA

Spadini, D., Palomba, F., Baum, T., Hanenberg, S., Bruntink, M., & Bacchelli, A. (Accepted/In press). Test-Driven Code Review: An Empirical Study. In Proceedings of the 41st ACM/IEEE International Conference on Software Engineering https://doi.org/10.5281/zenodo.2551217

Vancouver

Spadini D, Palomba F, Baum T, Hanenberg S, Bruntink M, Bacchelli A. Test-Driven Code Review: An Empirical Study. In Proceedings of the 41st ACM/IEEE International Conference on Software Engineering. 2019 https://doi.org/10.5281/zenodo.2551217

Author

Spadini, Davide ; Palomba, Fabio ; Baum, Tobias ; Hanenberg, Stefan ; Bruntink, Magiel ; Bacchelli, Alberto. / Test-Driven Code Review: An Empirical Study. Proceedings of the 41st ACM/IEEE International Conference on Software Engineering. 2019.

BibTeX

@inproceedings{b275d9ed47b7432a8d224e1456a9ff7c,
title = "Test-Driven Code Review: An Empirical Study",
abstract = "Test-Driven Code Review (TDR) is a code review practice in which a reviewer inspects a patch by examining the changed test code before the changed production code. Although this practice has been mentioned positively by practitioners in informal literature and interviews, there is no systematic knowledge of its effects, prevalence, problems, and advantages.In this paper, we aim at empirically understanding whether this practice has an effect on code review effectiveness and how developers' perceive TDR. We conduct (i) a controlled experiment with 93 developers that perform more than 150 reviews, and (ii) 9 semi-structured interviews and a survey with 103 respondents to gather information on how TDR is perceived. Key results from the experiment show that developers adopting TDR find the same proportion of defects in production code, but more in test code, at the expenses of fewer maintainability issues in production code. Furthermore, we found that most developers prefer to review production code as they deem it more critical and tests should follow from it. Moreover, general poor test code quality and no tool support hinder the adoption of TDR. Public preprint: https://doi.org/10.5281/zenodo.2551217, data and materials: https://doi.org/10.5281/zenodo.2553139.",
author = "Davide Spadini and Fabio Palomba and Tobias Baum and Stefan Hanenberg and Magiel Bruntink and Alberto Bacchelli",
year = "2019",
doi = "10.5281/zenodo.2551217",
language = "English",
booktitle = "Proceedings of the 41st ACM/IEEE International Conference on Software Engineering",

}

RIS

TY - GEN

T1 - Test-Driven Code Review: An Empirical Study

AU - Spadini, Davide

AU - Palomba, Fabio

AU - Baum, Tobias

AU - Hanenberg, Stefan

AU - Bruntink, Magiel

AU - Bacchelli, Alberto

PY - 2019

Y1 - 2019

N2 - Test-Driven Code Review (TDR) is a code review practice in which a reviewer inspects a patch by examining the changed test code before the changed production code. Although this practice has been mentioned positively by practitioners in informal literature and interviews, there is no systematic knowledge of its effects, prevalence, problems, and advantages.In this paper, we aim at empirically understanding whether this practice has an effect on code review effectiveness and how developers' perceive TDR. We conduct (i) a controlled experiment with 93 developers that perform more than 150 reviews, and (ii) 9 semi-structured interviews and a survey with 103 respondents to gather information on how TDR is perceived. Key results from the experiment show that developers adopting TDR find the same proportion of defects in production code, but more in test code, at the expenses of fewer maintainability issues in production code. Furthermore, we found that most developers prefer to review production code as they deem it more critical and tests should follow from it. Moreover, general poor test code quality and no tool support hinder the adoption of TDR. Public preprint: https://doi.org/10.5281/zenodo.2551217, data and materials: https://doi.org/10.5281/zenodo.2553139.

AB - Test-Driven Code Review (TDR) is a code review practice in which a reviewer inspects a patch by examining the changed test code before the changed production code. Although this practice has been mentioned positively by practitioners in informal literature and interviews, there is no systematic knowledge of its effects, prevalence, problems, and advantages.In this paper, we aim at empirically understanding whether this practice has an effect on code review effectiveness and how developers' perceive TDR. We conduct (i) a controlled experiment with 93 developers that perform more than 150 reviews, and (ii) 9 semi-structured interviews and a survey with 103 respondents to gather information on how TDR is perceived. Key results from the experiment show that developers adopting TDR find the same proportion of defects in production code, but more in test code, at the expenses of fewer maintainability issues in production code. Furthermore, we found that most developers prefer to review production code as they deem it more critical and tests should follow from it. Moreover, general poor test code quality and no tool support hinder the adoption of TDR. Public preprint: https://doi.org/10.5281/zenodo.2551217, data and materials: https://doi.org/10.5281/zenodo.2553139.

U2 - 10.5281/zenodo.2551217

DO - 10.5281/zenodo.2551217

M3 - Conference contribution

BT - Proceedings of the 41st ACM/IEEE International Conference on Software Engineering

ER -

ID: 51391073