RUcore Resource Object
RUcore Resource Object
PDF-1(558.98 KB)
Uniform TitleCrisp - a fault localization tool for Java programs
NameChesley, Ophelia (author), Ryder, Barbara (chair), Kremer, Ulrich (internal member), Smith, Donald (internal member), Rutgers University, Graduate School - New Brunswick,
Degree Date2007
Date Created2007
SubjectComputer Science,
Java (Computer program language),
Electronic circuits
DescriptionCrisp is a tool (i.e., an Eclipse plug-in) for constructing intermediate versions of a Java
program that is being edited in an IDE such as Eclipse. After a long editing session, a programmer usually will run regression tests to make sure she has not invalidated previously checked functionality. If a test fails unexpectedly, Crisp uses input from Chianti, a tool for semantic change impact analysis [13], to allow the programmer to select parts of the edit that affected the failing test and to add them to the original program, creating an intermediate version guaranteed to compile. Then the programmer can re-execute the test in order to locate the exact reasons for the failure by concentrating on those affecting changes that were applied. Using Crisp, a programmer can 1) iteratively select, apply, and undo individual (or sets of) affecting changes and, thus effectively find a small set of failure-inducing changes, or 2) request Crisp to automatically suggest a set of failure-inducing changes.
program that is being edited in an IDE such as Eclipse. After a long editing session, a programmer usually will run regression tests to make sure she has not invalidated previously checked functionality. If a test fails unexpectedly, Crisp uses input from Chianti, a tool for semantic change impact analysis [13], to allow the programmer to select parts of the edit that affected the failing test and to add them to the original program, creating an intermediate version guaranteed to compile. Then the programmer can re-execute the test in order to locate the exact reasons for the failure by concentrating on those affecting changes that were applied. Using Crisp, a programmer can 1) iteratively select, apply, and undo individual (or sets of) affecting changes and, thus effectively find a small set of failure-inducing changes, or 2) request Crisp to automatically suggest a set of failure-inducing changes.
NoteM.S.
NoteIncludes bibliographical references (p. 74-75).
Genretheses
Persistent URLhttp://hdl.rutgers.edu/1782.2/rucore10001600001.ETD.15801
LanguageEnglish
CollectionGraduate School - New Brunswick Electronic Theses and Dissertations
Organization NameRutgers, The State University of New Jersey
RightsThe author owns the copyright to this work.