Tests that fail inconsistently, without changes to the code under test, are described as flaky.
Flaky tests do not give a clear indication of the presence of software bugs and thus limit the …

Context: Software regression testing refers to rerunning test cases after the system under
test is modified, ascertaining that the changes have not (re-) introduced failures. Not all …

A flaky test is a test that may lead to different results in different runs on a single code under
test without any change in the test code. Test flakiness is a noxious phenomenon that slows …

Continuous integration testing is an important step in the modern software engineering life
cycle. Test prioritization is a method that can improve the efficiency of continuous integration …

Regression test selection (RTS) and prioritization (RTP) techniques aim to reduce testing
efforts and developer feedback time after a change to the code base. Using various …

Continuous Integration (CI) is a popular practice in modern software engineering.
Unfortunately, it is also a high-cost practice—Google and Mozilla estimate their CI systems …

To facilitate the rapid release cadence of modern software (on the order of weeks, days, or
even hours), software development organizations invest in practices like Continuous …

Continuous integration advocates to run the test suite of a project frequently, eg, for every
code change committed to a shared repository. This process imposes a high computational …

At IVU Traffic Technologies, continuous integration (CI) pipelines build, analyze, and test the
code for inadvertent effects before pull requests are merged. However, compiling the entire …

Today's software failures have two dominating root causes: code bugs and
misconfigurations. To combat failure-inducing software changes, unified regression testing …