Chianti: a tool for change impact analysis of java programs

By Xiaoxia Ren, Fenil Shah, Frank Tip, B. Ryder, Ophelia C. Chesley. Conference on Object-Oriented Programming Systems, Languages, and Applications, 2004

455 citations recorded by the source corpus.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/820fccef5adbbabd20bba38d501ab4a2fc878261

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Software

Citations in the corpus

Software development with real-time collaborative editing (2012, methodology): “In the context of software development, change impact analysis computes the set of unit tests impacted by a collection of code changes [42] and was implemented in Chianti [41]; and safe-commit analysis determines code changes that can safely be committed to version control without breaking tests [57”
A systematic review on regression test selection techniques (2010, methodology): “Examples include test case selection based on code changes [1][6][13][17][20][22][43][49][62][64][67] and specification changes [38][40][54][68], evaluation of selection techniques [48], change impact analysis [44], regression tests for different applications e.”
Asking and Answering Questions during a Programming Change Task (2008, methodology): “For example, Fyson and Boldyreff show how this can be done using program understanding techniques to populate a ripple propagation graph [24] and Chianti is a tool that uses a suite of unit tests to generate a list of affected unit tests given a change to a system [74].”
Differential symbolic execution (2008, methodology): “Chianti:a change impact analysis tool for Java programs.”