Standard

When Testing Meets Code Review : Why and How Developers Review Tests. / Spadini, Davide; Aniche, Maurício; Storey, Margaret-Anne; Bruntink, Magiel; Bacchelli, Alberto.

Proceedings of the 40th International Conference on Software Engineering, ICSE '18. New York, NY : Association for Computing Machinery (ACM), 2018. p. 677-687.

Research output: Scientific - peer-reviewConference contribution

Harvard

Spadini, D, Aniche, M, Storey, M-A, Bruntink, M & Bacchelli, A 2018, When Testing Meets Code Review: Why and How Developers Review Tests. in Proceedings of the 40th International Conference on Software Engineering, ICSE '18. Association for Computing Machinery (ACM), New York, NY, pp. 677-687, ICSE 2018, Gothenburg, Sweden, 27/05/18. DOI: 10.1145/3180155.3180192

APA

Spadini, D., Aniche, M., Storey, M-A., Bruntink, M., & Bacchelli, A. (2018). When Testing Meets Code Review: Why and How Developers Review Tests. In Proceedings of the 40th International Conference on Software Engineering, ICSE '18 (pp. 677-687). New York, NY: Association for Computing Machinery (ACM). DOI: 10.1145/3180155.3180192

Vancouver

Spadini D, Aniche M, Storey M-A, Bruntink M, Bacchelli A. When Testing Meets Code Review: Why and How Developers Review Tests. In Proceedings of the 40th International Conference on Software Engineering, ICSE '18. New York, NY: Association for Computing Machinery (ACM). 2018. p. 677-687. Available from, DOI: 10.1145/3180155.3180192

Author

Spadini, Davide ; Aniche, Maurício ; Storey, Margaret-Anne ; Bruntink, Magiel ; Bacchelli, Alberto. / When Testing Meets Code Review : Why and How Developers Review Tests. Proceedings of the 40th International Conference on Software Engineering, ICSE '18. New York, NY : Association for Computing Machinery (ACM), 2018. pp. 677-687

BibTeX

@inbook{256e7d56352f44ae919b97fad0eafe69,
title = "When Testing Meets Code Review: Why and How Developers Review Tests",
abstract = "Automated testing is considered an essential process for ensuring software quality. However, writing and maintaining high-quality test code is challenging and frequently considered of secondary importance. For production code, many open source and industrial software projects employ code review, a well-established software quality practice, but the question remains whether and how code review is also used for ensuring the quality of test code. The aim of this research is to answer this question and to increase our understanding of what developers think and do when it comes to reviewing test code. We conducted both quantitative and qualitative methods to analyze more than 300,000 code reviews, and interviewed 12 developers about how they review test files. This work resulted in an overview of current code reviewing practices, a set of identified obstacles limiting the review of test code, and a set of issues that developers would like to see improved in code review tools. The study reveals that reviewing test files is very different from reviewing production files, and that the navigation within the review itself is one of the main issues developers currently face. Based on our findings, we propose a series of recommendations and suggestions for the design of tools and future research.",
keywords = "software testing, automated testing, code review, Gerrit",
author = "Davide Spadini and Maurício Aniche and Margaret-Anne Storey and Magiel Bruntink and Alberto Bacchelli",
note = "Accepted Author Manuscript",
year = "2018",
doi = "10.1145/3180155.3180192",
pages = "677--687",
booktitle = "Proceedings of the 40th International Conference on Software Engineering, ICSE '18",
publisher = "Association for Computing Machinery (ACM)",
address = "United States",

}

RIS

TY - CHAP

T1 - When Testing Meets Code Review

T2 - Why and How Developers Review Tests

AU - Spadini,Davide

AU - Aniche,Maurício

AU - Storey,Margaret-Anne

AU - Bruntink,Magiel

AU - Bacchelli,Alberto

N1 - Accepted Author Manuscript

PY - 2018

Y1 - 2018

N2 - Automated testing is considered an essential process for ensuring software quality. However, writing and maintaining high-quality test code is challenging and frequently considered of secondary importance. For production code, many open source and industrial software projects employ code review, a well-established software quality practice, but the question remains whether and how code review is also used for ensuring the quality of test code. The aim of this research is to answer this question and to increase our understanding of what developers think and do when it comes to reviewing test code. We conducted both quantitative and qualitative methods to analyze more than 300,000 code reviews, and interviewed 12 developers about how they review test files. This work resulted in an overview of current code reviewing practices, a set of identified obstacles limiting the review of test code, and a set of issues that developers would like to see improved in code review tools. The study reveals that reviewing test files is very different from reviewing production files, and that the navigation within the review itself is one of the main issues developers currently face. Based on our findings, we propose a series of recommendations and suggestions for the design of tools and future research.

AB - Automated testing is considered an essential process for ensuring software quality. However, writing and maintaining high-quality test code is challenging and frequently considered of secondary importance. For production code, many open source and industrial software projects employ code review, a well-established software quality practice, but the question remains whether and how code review is also used for ensuring the quality of test code. The aim of this research is to answer this question and to increase our understanding of what developers think and do when it comes to reviewing test code. We conducted both quantitative and qualitative methods to analyze more than 300,000 code reviews, and interviewed 12 developers about how they review test files. This work resulted in an overview of current code reviewing practices, a set of identified obstacles limiting the review of test code, and a set of issues that developers would like to see improved in code review tools. The study reveals that reviewing test files is very different from reviewing production files, and that the navigation within the review itself is one of the main issues developers currently face. Based on our findings, we propose a series of recommendations and suggestions for the design of tools and future research.

KW - software testing

KW - automated testing

KW - code review

KW - Gerrit

UR - http://resolver.tudelft.nl/uuid:256e7d56-352f-44ae-919b-97fad0eafe69

U2 - 10.1145/3180155.3180192

DO - 10.1145/3180155.3180192

M3 - Conference contribution

SP - 677

EP - 687

BT - Proceedings of the 40th International Conference on Software Engineering, ICSE '18

PB - Association for Computing Machinery (ACM)

ER -

ID: 38853936