Program slicing is a well-known technique that utilizes dependency graphs and static program analysis. Our goal is to perform change impact analysis of Erlang programs based on the resulted program slices, that is we want to measure the impact of any change made on the source code: especially we want to select a subset of test cases which must be rerun after the modification. The change can be performed manually by the programmer or using a refactoring tool, such as RefactorErl. However refactorings should preserve the original behaviour of the system, developers want to be convinced about that, thus they retest the software after some transformations. Software testing is said to be the most expensive part of the lifecycle of software systems, so our research focuses on selecting test cases affected by refactorings that should be retested after the transformation.
Audience: Erlang developers and researchers
Objectives: Show the audience how you can use the change impact analysis technique to detect the subset of test cases affected by a change on the source code.