Conference paper Open Access

How Effective is Continuous Integration in Indicating Single-Statement Bugs?

Latendresse, Jasmine; Costa, Diego Elias; Abdalkareem, Rabe; Shihab, Emad

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="DOI">10.5281/zenodo.4606679</identifier>
      <creatorName>Latendresse, Jasmine</creatorName>
      <affiliation>Concordia University, Canada</affiliation>
      <creatorName>Costa, Diego Elias</creatorName>
      <givenName>Diego Elias</givenName>
      <affiliation>Concordia University, Canada</affiliation>
      <creatorName>Abdalkareem, Rabe</creatorName>
      <affiliation>Queen's University, Canada</affiliation>
      <creatorName>Shihab, Emad</creatorName>
      <affiliation>Concordia University, Canada</affiliation>
    <title>How Effective is Continuous Integration in Indicating Single-Statement Bugs?</title>
    <subject>Software Engineering, Continuous Integration</subject>
    <date dateType="Issued">2021-03-08</date>
  <resourceType resourceTypeGeneral="ConferencePaper"/>
    <alternateIdentifier alternateIdentifierType="url"></alternateIdentifier>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsVersionOf">10.5281/zenodo.4606678</relatedIdentifier>
    <rights rightsURI="">Creative Commons Attribution 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&lt;p&gt;Continuous Integration (CI) is the process of auto-matically compiling, building, and testing code changes in the hope of catching bugs as they are introduced into the code base. With bug fixing being a core and increasingly costly task in software development, the community has adopted CI to mitigate this issue and improve the quality of their software products. Bug fixing is a core task in software development and becomes increasingly costly over time. However, little is known about how effective CI is at detecting simple, single-statement bugs.&lt;/p&gt;

&lt;p&gt;In this paper, we analyze the effectiveness of CI in 14 popular open source Java-based projects to warn about 318 single-statement bugs (SStuBs). We analyze the build status at the commits that introduce SStuBs and before the SStuBs were fixed. We then investigate how often CI indicates the presence of these bugs, through test failure. Our results show that only 2% of the commits that introduced SStuBs have builds with failed tests and 7.5% of builds before the fix reported test failures. Upon close manual inspection, we found that none of the failed builds actually captured SStuBs, indicating that CI is not the right medium to capture the SStuBs we studied. Our results suggest that developers should not rely on CI to catch SStuBs or increase their CI pipeline coverage to detect single-statement bugs.&lt;/p&gt;</description>
All versions This version
Views 613613
Downloads 293293
Data volume 72.2 MB72.2 MB
Unique views 559559
Unique downloads 278278


Cite as