Standard

When, how, and why developers (do not) test in their IDEs. / Beller, Moritz; Gousios, Georgios; Panichella, Annibale; Zaidman, Andy.

2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings. Association for Computing Machinery (ACM), 2015. p. 179-190.

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

Harvard

Beller, M, Gousios, G, Panichella, A & Zaidman, A 2015, When, how, and why developers (do not) test in their IDEs. in 2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings. Association for Computing Machinery (ACM), pp. 179-190, 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015, Bergamo, Italy, 30/08/15. https://doi.org/10.1145/2786805.2786843

APA

Beller, M., Gousios, G., Panichella, A., & Zaidman, A. (2015). When, how, and why developers (do not) test in their IDEs. In 2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings (pp. 179-190). Association for Computing Machinery (ACM). https://doi.org/10.1145/2786805.2786843

Vancouver

Beller M, Gousios G, Panichella A, Zaidman A. When, how, and why developers (do not) test in their IDEs. In 2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings. Association for Computing Machinery (ACM). 2015. p. 179-190 https://doi.org/10.1145/2786805.2786843

Author

Beller, Moritz ; Gousios, Georgios ; Panichella, Annibale ; Zaidman, Andy. / When, how, and why developers (do not) test in their IDEs. 2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings. Association for Computing Machinery (ACM), 2015. pp. 179-190

BibTeX

@inproceedings{31fcb772aca44892913cf30f2182d87e,
title = "When, how, and why developers (do not) test in their IDEs",
abstract = "The research community in Software Engineering and Software Testing in particular builds many of its contributions on a set of mutually shared expectations. Despite the fact that they form the basis of many publications as well as open-source and commercial testing applications, these common expectations and beliefs are rarely ever questioned. For example, Frederic Brooks' statement that testing takes half of the development time seems to have manifested itself within the community since he first made it in the {"}Mythical Man Month{"} in 1975. With this paper, we report on the surprising results of a large-scale field study with 416 software engineers whose development activity we closely monitored over the course of five months, resulting in over 13 years of recorded work time in their integrated development environments (IDEs). Our findings question several commonly shared assumptions and beliefs about testing and might be contributing factors to the observed bug proneness of software in practice: The majority of developers in our study does not test; developers rarely run their tests in the IDE; Test-Driven Development (TDD) is not widely practiced; and, last but not least, software developers only spend a quarter of their work time engineering tests, whereas they think they test half of their time.",
keywords = "Developer testing, Field study, Test- driven development (TDD), Testing effort, Unit tests",
author = "Moritz Beller and Georgios Gousios and Annibale Panichella and Andy Zaidman",
year = "2015",
month = "8",
day = "30",
doi = "10.1145/2786805.2786843",
language = "English",
pages = "179--190",
booktitle = "2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings",
publisher = "Association for Computing Machinery (ACM)",
address = "United States",

}

RIS

TY - GEN

T1 - When, how, and why developers (do not) test in their IDEs

AU - Beller, Moritz

AU - Gousios, Georgios

AU - Panichella, Annibale

AU - Zaidman, Andy

PY - 2015/8/30

Y1 - 2015/8/30

N2 - The research community in Software Engineering and Software Testing in particular builds many of its contributions on a set of mutually shared expectations. Despite the fact that they form the basis of many publications as well as open-source and commercial testing applications, these common expectations and beliefs are rarely ever questioned. For example, Frederic Brooks' statement that testing takes half of the development time seems to have manifested itself within the community since he first made it in the "Mythical Man Month" in 1975. With this paper, we report on the surprising results of a large-scale field study with 416 software engineers whose development activity we closely monitored over the course of five months, resulting in over 13 years of recorded work time in their integrated development environments (IDEs). Our findings question several commonly shared assumptions and beliefs about testing and might be contributing factors to the observed bug proneness of software in practice: The majority of developers in our study does not test; developers rarely run their tests in the IDE; Test-Driven Development (TDD) is not widely practiced; and, last but not least, software developers only spend a quarter of their work time engineering tests, whereas they think they test half of their time.

AB - The research community in Software Engineering and Software Testing in particular builds many of its contributions on a set of mutually shared expectations. Despite the fact that they form the basis of many publications as well as open-source and commercial testing applications, these common expectations and beliefs are rarely ever questioned. For example, Frederic Brooks' statement that testing takes half of the development time seems to have manifested itself within the community since he first made it in the "Mythical Man Month" in 1975. With this paper, we report on the surprising results of a large-scale field study with 416 software engineers whose development activity we closely monitored over the course of five months, resulting in over 13 years of recorded work time in their integrated development environments (IDEs). Our findings question several commonly shared assumptions and beliefs about testing and might be contributing factors to the observed bug proneness of software in practice: The majority of developers in our study does not test; developers rarely run their tests in the IDE; Test-Driven Development (TDD) is not widely practiced; and, last but not least, software developers only spend a quarter of their work time engineering tests, whereas they think they test half of their time.

KW - Developer testing

KW - Field study

KW - Test- driven development (TDD)

KW - Testing effort

KW - Unit tests

UR - http://www.scopus.com/inward/record.url?scp=84960395903&partnerID=8YFLogxK

U2 - 10.1145/2786805.2786843

DO - 10.1145/2786805.2786843

M3 - Conference contribution

SP - 179

EP - 190

BT - 2015 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2015 - Proceedings

PB - Association for Computing Machinery (ACM)

ER -

ID: 8928230