Software changes, such as bug fixes or feature additions, can introduce software bugs and reduce the code quality. As a result tests which passed earlier may not pass any more-thereby exposing a regression in software behavior. This survey overviews recent advances in determining the impact of the code changes onto the program's behavior and other syntactic program artifacts. Static program analysis can help determining change impact in an approximate manner while dynamic analysis determines change impact more precisely but requires a regression test suite. Moreover, as the program is changed, the corresponding test suite may, too. Some tests may become obsolete while other tests are to be augmented that stress the changes. This article sur...
Software architectures are becoming centric to the development of quality software systems, being th...
This paper presents a new methodology to select test cases from regression test suites. The selectio...
The activity of re-testing of only those parts of the program or code, in which some modifications a...
Changes often introduce program errors, and hence recent software testing literature has focused on ...
Regression testing is an expensive process because, most of times, all the avail-able test cases are...
Software testing is an expensive and time-consuming process, often involving the manual creation of ...
This paper presents a regression testing framework for object-oriented software based on extended sy...
Regression testing is an expensive process because, most of times, all the available test cases are ...
International audienceAspect-oriented software evolution introduces new challenges for regression te...
Software systems is evolve continuously during development and maintenance. After software is modifi...
Developers evolve a software system by changing the pro-gram source code, by modifying its context b...
Regression testing is an expensive but necessary maintenance activity performed on modified software...
Small changes can have major and nonlocal effects in object oriented languages, due to the extensive...
Part 4: Testing Methods and AutomationInternational audienceWithin the context of software evolution...
One of the most important activities in software maintenance is Regression testing. The re-execution...
Software architectures are becoming centric to the development of quality software systems, being th...
This paper presents a new methodology to select test cases from regression test suites. The selectio...
The activity of re-testing of only those parts of the program or code, in which some modifications a...
Changes often introduce program errors, and hence recent software testing literature has focused on ...
Regression testing is an expensive process because, most of times, all the avail-able test cases are...
Software testing is an expensive and time-consuming process, often involving the manual creation of ...
This paper presents a regression testing framework for object-oriented software based on extended sy...
Regression testing is an expensive process because, most of times, all the available test cases are ...
International audienceAspect-oriented software evolution introduces new challenges for regression te...
Software systems is evolve continuously during development and maintenance. After software is modifi...
Developers evolve a software system by changing the pro-gram source code, by modifying its context b...
Regression testing is an expensive but necessary maintenance activity performed on modified software...
Small changes can have major and nonlocal effects in object oriented languages, due to the extensive...
Part 4: Testing Methods and AutomationInternational audienceWithin the context of software evolution...
One of the most important activities in software maintenance is Regression testing. The re-execution...
Software architectures are becoming centric to the development of quality software systems, being th...
This paper presents a new methodology to select test cases from regression test suites. The selectio...
The activity of re-testing of only those parts of the program or code, in which some modifications a...