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

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 (CI) requires efficient regression testing to ensure software quality
without significantly delaying its CI builds. This warrants the need for techniques to reduce …

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

Automated testing is an essential component of Continuous Integration (CI) and Delivery
(CD), such as scheduling automated test sessions on overnight builds. That allows …

Test case prioritization (TCP) is a practical activity in software testing for exposing faults
earlier. Researchers have proposed many TCP techniques to reorder test cases. Among …

Software testing is a strenuous and expensive process. At least 50% of the total software
cost is spent on testing activities [12]. Companies are often faced with time and resource …

The large body of existing research in Test Case Prioritization (TCP) techniques, can be
broadly classified into two categories: dynamic techniques (that rely on run-time execution …

Continuous Integration (CI) environments have been increasingly adopted in the industry to
allow frequent integration of software changes, making software evolution faster and cost …

Continuous integration refers to the practice of merging the working copies of all developers
into the mainline frequently. Regression testing for each mergence is characterized by …