
The aim of this paper is to describe a way to construct tests which validate that changes made during software evolution did not introduce regression faults. Developers usually run a new version of the program against the same set of tests. In order to achieve this goal, symbolic execution was used for test input generation and full structural code coverage. Moreover, the extension of symbolic execution was developed to increase the quality of tests. As a result, regression faults were detected in the program. The concept of the technique and an example model are presented. Ill. 7, bibl. 18 (in English; abstracts in English and Lithuanian).http://dx.doi.org/10.5755/j01.eee.112.6.457
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
