Abstract Context: Continuous Integration (CI) environments allow frequent integration of
software changes, making software evolution more rapid and cost-effective. In such …

Software fault localization, the act of identifying the locations of faults in a program, is widely
recognized to be one of the most tedious, time consuming, and expensive-yet equally critical …

In continuous integration development environments, software engineers frequently
integrate new or changed code with the mainline codebase. This can reduce the amount of …

An important research area of Spectrum-Based Fault Localization (SBFL) is the
effectiveness of risk evaluation formulas. Most previous studies have adopted an empirical …

Software testing is undertaken to ensure that the software meets the expected requirements.
The intention is to find bugs, errors, or defects in the developed software so that they can be …

Regression testing assures changed programs against unintended amendments.
Rearranging the execution order of test cases is a key idea to improve their effectiveness …

Fault-localization techniques that apply statistical analyses to execution data gathered from
multiple tests are quite effective when a large test suite is available. However, if no test suite …

Continuous integration (CI) development environments allow software engineers to
frequently integrate and test their code. While CI environments provide advantages, they …

Keeping evolving systems fault free is hard. Change impact analysis is a well-studied
methodology for finding faults in evolving systems. For example, in order to help developers …

Test case prioritization techniques seek to maximize early fault detection. Fault localization
seeks to use test cases already executed to help find the fault location. There is a natural …