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 …

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

Developers rely on regression testing in their continuous integration (CI) environment to find
changes that introduce regression faults. While regression testing is widely practiced, it can …

Continuous integration (CI) systems perform the automated build, test execution, and
delivery of the software. CI can provide fast feedback on software changes, minimizing the …

Software defects cost time and money to diagnose and fix. Consequently, developers use a
variety of techniques to avoid introducing defects into their systems. However, these …

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 …

Testing in Continuous Integration (CI) involves test case prioritization, selection, and
execution at each cycle. Selecting the most promising test cases to detect bugs is hard if …

Continuous integration, at its core, includes a set of practices that aim to prevent and reduce
the cost of software integration issues by merging working software copies often. Regression …

Two heuristics namely diversity-based (DBTP) and history-based test prioritization (HBTP)
have been separately proposed in the literature. Yet, their combination has not been widely …

Continuous Integration (CI) requires efficient regression testing to ensure software quality
without significantly delaying its CI builds. This warrants the need for techniques to reduce …