Selecting manual regression test cases automatically using trace link recovery and change coverage

S. Eder, B. Hauptmann, Maximilian Junker, Rudolf Vaas, Karl-Heinz Prommer
{"title":"Selecting manual regression test cases automatically using trace link recovery and change coverage","authors":"S. Eder, B. Hauptmann, Maximilian Junker, Rudolf Vaas, Karl-Heinz Prommer","doi":"10.1145/2593501.2593506","DOIUrl":null,"url":null,"abstract":"Regression tests ensure that existing functionality is not impaired by changes to an existing software system. However, executing complete test suites often takes much time. Therefore, a subset of tests has to be found that is sufficient to validate whether the system under test is still valid after it has been changed. This test case selection is especially important if regression tests are executed manually, since manual execution is time intensive and costly. To select manual test cases, many regression testing techniques exist that aim on achieving coverage of changed or even new code. Many of these techniques base on coverage data from prior test runs or logical properties such as annotated pre and post conditions in the source code. However, coverage information becomes outdated if a system is changed extensively. Also annotated logical properties are often not available in industrial software systems. We present an approach for test selection that is based on static analyses of the test suite and the system's source code. We combine trace link recovery using latent semantic indexing with the metric change coverage, which assesses the coverage of source code changes. The proposed approach works automatically without the need to execute tests beforehand or annotate source code. Furthermore, we present a first evaluation of the approach.","PeriodicalId":443108,"journal":{"name":"International Conference/Workshop on Automation of Software Test","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2014-05-31","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"International Conference/Workshop on Automation of Software Test","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/2593501.2593506","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 7

Abstract

Regression tests ensure that existing functionality is not impaired by changes to an existing software system. However, executing complete test suites often takes much time. Therefore, a subset of tests has to be found that is sufficient to validate whether the system under test is still valid after it has been changed. This test case selection is especially important if regression tests are executed manually, since manual execution is time intensive and costly. To select manual test cases, many regression testing techniques exist that aim on achieving coverage of changed or even new code. Many of these techniques base on coverage data from prior test runs or logical properties such as annotated pre and post conditions in the source code. However, coverage information becomes outdated if a system is changed extensively. Also annotated logical properties are often not available in industrial software systems. We present an approach for test selection that is based on static analyses of the test suite and the system's source code. We combine trace link recovery using latent semantic indexing with the metric change coverage, which assesses the coverage of source code changes. The proposed approach works automatically without the need to execute tests beforehand or annotate source code. Furthermore, we present a first evaluation of the approach.
使用跟踪链接恢复和变更覆盖自动选择手动回归测试用例
回归测试确保现有的功能不会因对现有软件系统的更改而受损。然而,执行完整的测试套件通常需要花费很多时间。因此,必须找到一个测试子集,它足以验证被测系统在被更改后是否仍然有效。如果回归测试是手动执行的,那么这个测试用例的选择是特别重要的,因为手动执行是费时且昂贵的。为了选择手动测试用例,存在许多回归测试技术,其目的是实现已更改或甚至新代码的覆盖。这些技术中的许多都基于来自先前测试运行的覆盖率数据或逻辑属性,例如源代码中带注释的前后条件。然而,如果系统被广泛地更改,覆盖信息就会过时。此外,在工业软件系统中通常不提供带注释的逻辑属性。我们提出了一种基于测试套件和系统源代码的静态分析的测试选择方法。我们将使用潜在语义索引的跟踪链接恢复与度量变更覆盖率相结合,度量变更覆盖率评估源代码变更的覆盖率。所建议的方法可以自动工作,而不需要事先执行测试或注释源代码。此外,我们对该方法进行了首次评估。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信