DeFlaker automatically detecting flaky tests

J Bell, O Legunsen, M Hilton, L Eloussi… - Proceedings of the 40th …, 2018 - dl.acm.org
Developers often run tests to check that their latest changes to a code repository did not
break any previously working functionality. Ideally, any new test failures would indicate …

Practical test dependency detection

A Gambi, J Bell, A Zeller - 2018 IEEE 11th International …, 2018 - ieeexplore.ieee.org
Regression tests should consistently produce the same outcome when executed against the
same version of the system under test. Recent studies, however, show a different picture: in …

We're doing it live: A multi-method empirical study on continuous experimentation

G Schermann, J Cito, P Leitner, U Zdun… - Information and Software …, 2018 - Elsevier
Context Continuous experimentation guides development activities based on data collected
on a subset of online users on a new experimental version of the software. It includes …

Automatically repairing dependency-related build breakage

C Macho, S McIntosh, M Pinzger - 2018 ieee 25th international …, 2018 - ieeexplore.ieee.org
Build systems are widely used in today's software projects to automate integration and build
processes. Similar to source code, build specifications need to be maintained to avoid …

Use and misuse of continuous integration features: An empirical study of projects that (mis) use Travis CI

K Gallaba, S McIntosh - IEEE Transactions on Software …, 2018 - ieeexplore.ieee.org
Continuous Integration (CI) is a popular practice where software systems are automatically
compiled and tested as changes appear in the version control system of a project. Like other …

Continuous code quality: Are we (really) doing that?

C Vassallo, F Palomba, A Bacchelli… - Proceedings of the 33rd …, 2018 - dl.acm.org
Continuous Integration (CI) is a software engineering practice where developers constantly
integrate their changes to a project through an automated build process. The goal of CI is to …

Noise and heterogeneity in historical build data: an empirical study of travis ci

K Gallaba, C Macho, M Pinzger… - Proceedings of the 33rd …, 2018 - dl.acm.org
Automated builds, which may pass or fail, provide feedback to a development team about
changes to the codebase. A passing build indicates that the change compiles cleanly and …

One size does not fit all: an empirical study of containerized continuous deployment workflows

Y Zhang, B Vasilescu, H Wang, V Filkov - … of the 2018 26th ACM Joint …, 2018 - dl.acm.org
Continuous deployment (CD) is a software development practice aimed at automating
delivery and deployment of a software product, following any changes to its code. If properly …

Work practices and challenges in continuous integration: A survey with Travis CI users

G Pinto, F Castor, R Bonifacio… - Software: Practice and …, 2018 - Wiley Online Library
Continuous integration (CI) is a software development practice that has been gaining
increasing popularity in the last few years. However, we still miss a collection of experiences …

Mining container image repositories for software configuration and beyond

T Xu, D Marinov - Proceedings of the 40th International Conference on …, 2018 - dl.acm.org
This paper introduces the idea of mining container image repositories for configuration and
other deployment information of software systems. Unlike traditional software repositories …