|
Title
|
|
|
|
On the differences between unit and integration testing in the TravisTorrent dataset
|
|
|
Author
|
|
|
|
|
|
|
Abstract
|
|
|
|
| Already from the early days of testing, practitioners distinguish between unit tests and integration tests as a strategy to locate defects. Unfortunately, the mining software engineering community rarely distinguishes between these two strategies, mainly because it is not straightforward to separate them in the code repositories under study. In this paper we exploited the TravisTorrent dataset provided for the MSR 2017 mining challenge; separated unit tests from integration tests; and correlated these against the workflow as recorded in the corresponding issue reports. Further analysis confirmed that it is worthwhile to treat unit tests and integration tests differently: we discovered that unit tests cause more breaking builds, that fixing the defects exposed by unit tests takes longer and implies more coordination between team members. |
|
|
|
Language
|
|
|
|
English
|
|
|
Source (journal)
|
|
|
|
IEEE International Working Conference on Mining Software Repositories : [proceedings]. - Piscataway, NJ
|
|
|
|
|
|
|
MINING SOFTWARE REPOSITORIES (MSR 2017)
|
|
|
Source (book)
|
|
|
|
IEEE/ACM 14th International Conference on Mining Software Repositories, (MSR), MAY 20-21, 2017, Buenos Aires, ARGENTINA
|
|
|
Publication
|
|
|
|
New york
:
Ieee
,
2017
|
|
|
ISBN
|
|
|
|
978-1-5386-1544-7
|
|
|
|
|
|
|
978-1-5386-1544-7
|
|
|
DOI
|
|
|
|
10.1109/MSR.2017.25
|
|
|
Volume/pages
|
|
|
|
(2017)
, p. 451-454
|
|
|
ISI
|
|
|
|
000425917100046
|
|
|
Full text (Publisher's DOI)
|
|
|
|
|
|
|
Full text (publisher's version - intranet only)
|
|
|
|
|
|