Standard

Oops, My Tests Broke the Build : An Explorative Analysis of Travis CI with GitHub. / Beller, Moritz; Gousios, Georgios; Zaidman, Andy.

Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017. Los Alamitos, CA : IEEE, 2017. p. 356-367.

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

Harvard

Beller, M, Gousios, G & Zaidman, A 2017, Oops, My Tests Broke the Build: An Explorative Analysis of Travis CI with GitHub. in Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017. IEEE, Los Alamitos, CA, pp. 356-367, MSR 2017, Buenos Aires, Argentina, 20/05/17. https://doi.org/10.1109/MSR.2017.62

APA

Beller, M., Gousios, G., & Zaidman, A. (2017). Oops, My Tests Broke the Build: An Explorative Analysis of Travis CI with GitHub. In Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017 (pp. 356-367). Los Alamitos, CA: IEEE. https://doi.org/10.1109/MSR.2017.62

Vancouver

Beller M, Gousios G, Zaidman A. Oops, My Tests Broke the Build: An Explorative Analysis of Travis CI with GitHub. In Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017. Los Alamitos, CA: IEEE. 2017. p. 356-367 https://doi.org/10.1109/MSR.2017.62

Author

Beller, Moritz ; Gousios, Georgios ; Zaidman, Andy. / Oops, My Tests Broke the Build : An Explorative Analysis of Travis CI with GitHub. Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017. Los Alamitos, CA : IEEE, 2017. pp. 356-367

BibTeX

@inproceedings{35a824068e58492a8aaaa3aa201916d3,
title = "Oops, My Tests Broke the Build: An Explorative Analysis of Travis CI with GitHub",
abstract = "AbContinuous Integration (CI) has become a best practice of modern software development. Yet, at present, we have a shortfall of insight into the testing practices that are common in CI-based software development. In particular, weseek quantifiable evidence on how central testing is to the CI process, how strongly the project language influences testing, whether different integration environments are valuable and if testing on the CI can serve as a surrogate to local testing in the IDE. In an analysis of 2,640,825 Java and Ruby builds onTRAVIS CI, we find that testing is the single most important reason why builds fail. Moreover, the programming language has a strong influence on both the number of executed tests, their run time, and proneness to fail. The use of multiple integration environments leads to 10{\%} more failures being caught at build time. However, testing on TRAVIS CI does not seem an adequatesurrogate for running tests locally in the IDE. To further research on TRAVIS CI with GITHUB, we introduce TRAVISTORRENT.",
keywords = "Testing, Software, Java, Tools, Best practices, Programming",
author = "Moritz Beller and Georgios Gousios and Andy Zaidman",
year = "2017",
doi = "10.1109/MSR.2017.62",
language = "English",
pages = "356--367",
booktitle = "Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017",
publisher = "IEEE",
address = "United States",

}

RIS

TY - GEN

T1 - Oops, My Tests Broke the Build

T2 - An Explorative Analysis of Travis CI with GitHub

AU - Beller, Moritz

AU - Gousios, Georgios

AU - Zaidman, Andy

PY - 2017

Y1 - 2017

N2 - AbContinuous Integration (CI) has become a best practice of modern software development. Yet, at present, we have a shortfall of insight into the testing practices that are common in CI-based software development. In particular, weseek quantifiable evidence on how central testing is to the CI process, how strongly the project language influences testing, whether different integration environments are valuable and if testing on the CI can serve as a surrogate to local testing in the IDE. In an analysis of 2,640,825 Java and Ruby builds onTRAVIS CI, we find that testing is the single most important reason why builds fail. Moreover, the programming language has a strong influence on both the number of executed tests, their run time, and proneness to fail. The use of multiple integration environments leads to 10% more failures being caught at build time. However, testing on TRAVIS CI does not seem an adequatesurrogate for running tests locally in the IDE. To further research on TRAVIS CI with GITHUB, we introduce TRAVISTORRENT.

AB - AbContinuous Integration (CI) has become a best practice of modern software development. Yet, at present, we have a shortfall of insight into the testing practices that are common in CI-based software development. In particular, weseek quantifiable evidence on how central testing is to the CI process, how strongly the project language influences testing, whether different integration environments are valuable and if testing on the CI can serve as a surrogate to local testing in the IDE. In an analysis of 2,640,825 Java and Ruby builds onTRAVIS CI, we find that testing is the single most important reason why builds fail. Moreover, the programming language has a strong influence on both the number of executed tests, their run time, and proneness to fail. The use of multiple integration environments leads to 10% more failures being caught at build time. However, testing on TRAVIS CI does not seem an adequatesurrogate for running tests locally in the IDE. To further research on TRAVIS CI with GITHUB, we introduce TRAVISTORRENT.

KW - Testing

KW - Software

KW - Java

KW - Tools

KW - Best practices

KW - Programming

U2 - 10.1109/MSR.2017.62

DO - 10.1109/MSR.2017.62

M3 - Conference contribution

SP - 356

EP - 367

BT - Proceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017

PB - IEEE

CY - Los Alamitos, CA

ER -

ID: 21809639