Tools based on static analysis can be used to find defects in programs. Tools that do shallow
analyses based on pattern matching have existed since the 1980's and although they can …

Developers often run tests to check that their latest changes to a code repository did not
break any previously working functionality. Ideally, any new test failures would indicate …

Consider the execution of a failing program as a sequence of program states. Each state
induces the following state, up to the failure. Which variables and values of a program state …

This paper presents UMLDiff, an algorithm for automatically detecting structural changes
between the designs of subsequent versions of object-oriented software. It takes as input …

Sensitive data are increasingly available on-line through the Web and other distributed
protocols. This heightens the need to carefully control access to data. Control means not …

This paper reports on the design and implementation of Chianti, a change impact analysis
tool for Java that is implemented in the context of the Eclipse environment. Chianti analyzes …

Software change impact analysis (CIA) is a technique for identifying the effects of a change,
or estimating what needs to be modified to accomplish a change. Since the 1980s, there …

Impact analysis, determining when a change in one part of a program affects other parts of
the program, is time-consuming and problematic. Impact analysis is rarely used to predict …

The rigorous application of static timing analysis requires a large and costly amount of detail
knowledge on the hardware and software components of the system. Probabilistic Timing …

Regression test selection (RTS) aims to reduce regression testing time by only re-running
the tests affected by code changes. Prior research on RTS can be broadly split into dy namic …