Standard

Developer Testing in The IDE: Patterns, Beliefs, And Behavior. / Beller, Moritz; Zaidman, Andy; Gousios, Georgios; Panichella, Annibale.

In: IEEE Transactions on Software Engineering, 2018.

Research output: Scientific - peer-reviewArticle

Harvard

APA

Vancouver

Author

Beller, Moritz; Zaidman, Andy; Gousios, Georgios; Panichella, Annibale / Developer Testing in The IDE: Patterns, Beliefs, And Behavior.

In: IEEE Transactions on Software Engineering, 2018.

Research output: Scientific - peer-reviewArticle

BibTeX

@article{a63e79e0e0e448cd81ed87f163810538,
title = "Developer Testing in The IDE: Patterns, Beliefs, And Behavior",
keywords = "Developer testing, Developer tests, Test-Driven Development, Test-Guided Development",
author = "Moritz Beller and Andy Zaidman and Georgios Gousios and Annibale Panichella",
year = "2018",
doi = "10.1109/TSE.2017.2776152",
journal = "IEEE Transactions on Software Engineering",
issn = "0098-5589",
publisher = "Institute of Electrical and Electronics Engineers Inc.",

}

RIS

TY - JOUR

T1 - Developer Testing in The IDE: Patterns, Beliefs, And Behavior

AU - Beller,Moritz

AU - Zaidman,Andy

AU - Gousios,Georgios

AU - Panichella,Annibale

PY - 2018

Y1 - 2018

N2 - Software testing is one of the key activities to software quality in practice. Despite its importance, however, we have a remarkable lack of knowledge on how developers test in real-world projects. In this paper, we report on the surprising results of a large-scale field study with 2,443 software engineers whose development activities we closely monitored over the course of 2.5 years in four Integrated Development Environments (IDEs). Our findings question several commonly shared assumptions and beliefs about developer testing: half of the developers in our study does not test; developers rarely run their tests in the IDE; only once they start testing, do they do it heftily; most programming sessions end without any test execution; only a quarter of test cases is responsible for three quarters of all test failures; 12% of tests show flaky behavior; Test-Driven Development (TDD) is not widely practiced; and software developers only spend a quarter of their time engineering tests, whereas they think they test half of their time. We observed only minor differences in the testing practices among developers in different IDEs, Java, and C#. We summarize these practices of loosely guiding ones development efforts with the help of testing as Test-Guided Development (TGD).

AB - Software testing is one of the key activities to software quality in practice. Despite its importance, however, we have a remarkable lack of knowledge on how developers test in real-world projects. In this paper, we report on the surprising results of a large-scale field study with 2,443 software engineers whose development activities we closely monitored over the course of 2.5 years in four Integrated Development Environments (IDEs). Our findings question several commonly shared assumptions and beliefs about developer testing: half of the developers in our study does not test; developers rarely run their tests in the IDE; only once they start testing, do they do it heftily; most programming sessions end without any test execution; only a quarter of test cases is responsible for three quarters of all test failures; 12% of tests show flaky behavior; Test-Driven Development (TDD) is not widely practiced; and software developers only spend a quarter of their time engineering tests, whereas they think they test half of their time. We observed only minor differences in the testing practices among developers in different IDEs, Java, and C#. We summarize these practices of loosely guiding ones development efforts with the help of testing as Test-Guided Development (TGD).

KW - Developer testing

KW - Developer tests

KW - Test-Driven Development

KW - Test-Guided Development

U2 - 10.1109/TSE.2017.2776152

DO - 10.1109/TSE.2017.2776152

M3 - Article

JO - IEEE Transactions on Software Engineering

T2 - IEEE Transactions on Software Engineering

JF - IEEE Transactions on Software Engineering

SN - 0098-5589

ER -

ID: 38319274