Not logged in.
Quick Search - Contribution
Contribution Details
| Type | Conference or Workshop Paper |
| Scope | Discipline-based scholarship |
| Published in Proceedings | Yes |
| Title | When testing meets code review: why and how developers review tests |
| Organization Unit | |
| Authors |
|
| Presentation Type | paper |
| Item Subtype | Original Work |
| Refereed | Yes |
| Status | Published in final form |
| Language |
|
| ISBN | 9781450356381 |
| Page Range | 677 - 687 |
| Event Title | 40th International Conference on Software Engineering (ICSE) |
| Event Type | conference |
| Event Location | Gothenburg, Sweden |
| Event Start Date | June 27 - 2018 |
| Event End Date | July 3 - 2018 |
| Series Name | Proceedings of the International Conference on Software Engineering |
| Place of Publication | New York, New York, USA |
| Publisher | Association for Computing Machinery |
| Abstract Text | 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. |
| Related URLs |
|
| Digital Object Identifier | 10.1145/3180155.3180192 |
| Other Identification Number | merlin-id:16641 |
| PDF File |
Download from ZORA
|
| Export |
BibTeX
EP3 XML (ZORA)
|