2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM)最新文献

筛选

英文中文

Assessing the Impact of Execution Environment on Observation-Based Slicing 评估执行环境对基于观察的切片的影响

2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM) Pub Date : 2022-08-28 DOI: 10.1109/SCAM55253.2022.00010

D. Binkley, L. Moonen

{"title":"Assessing the Impact of Execution Environment on Observation-Based Slicing","authors":"D. Binkley, L. Moonen","doi":"10.1109/SCAM55253.2022.00010","DOIUrl":"https://doi.org/10.1109/SCAM55253.2022.00010","url":null,"abstract":"Program slicing reduces a program to a smaller version that retains a chosen computation, referred to as a slicing criterion. One recent multi-lingual slicing approach, observation-based slicing (ORBS), speculatively deletes parts of the program and then executes the code. If the behavior of the slicing criteria is unchanged, the speculative deletion is made permanent. While this makes ORBS language agnostic, it can lead to the production of some non-intuitive slices. One particular challenge is when the execution environment plays a role. For example, ORBS will delete the line “$mathrm{a}=0$” if the memory location assigned to a contains zero before executing this statement, because the deletion does not affect the value of a and thus the slicing criterion. Consequently, slices can differ between execution environments due to factors such as initialization and call stack reuse. The technique considered, $boldsymbol{n}$ VORBS, attempts to ameliorate this problem by validating a candidate slice in $boldsymbol{n}$ different execution environments. We conduct an empirical study to collect initial insights into how often the execution environment leads to slice differences. Specifically, we compare and contrast the slices produced by seven different instantiations of $boldsymbol{n}$ VORBS. Looking forward, the technique can be seen as a variation on metamorphic testing, and thus suggests how ideas from metamorphic testing might be used to improve dynamic program analysis.","PeriodicalId":138287,"journal":{"name":"2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM)","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-08-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131445161","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 1

Flaky Test Sanitisation via On-the-Fly Assumption Inference for Tests with Network Dependencies 基于网络依赖测试的动态假设推理的薄片测试消毒

2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM) Pub Date : 2022-08-01 DOI: 10.1109/SCAM55253.2022.00037

Jens Dietrich, Shawn Rasheed, Amjed Tahir

{"title":"Flaky Test Sanitisation via On-the-Fly Assumption Inference for Tests with Network Dependencies","authors":"Jens Dietrich, Shawn Rasheed, Amjed Tahir","doi":"10.1109/SCAM55253.2022.00037","DOIUrl":"https://doi.org/10.1109/SCAM55253.2022.00037","url":null,"abstract":"Flaky tests cause significant problems as they can interrupt automated build processes that rely on all tests succeeding and undermine the trustworthiness of tests. Numerous causes of test flakiness have been identified, and program analyses exist to detect such tests. Typically, these methods produce advice to developers on how to refactor tests in order to make test outcomes deterministic. We argue that one source of flakiness is the lack of assumptions that precisely describe under which circumstances a test is meaningful. We devise a sanitisation technique that can isolate flaky tests quickly by inferring such assumptions on-the-fly, allowing automated builds to proceed as flaky tests are ignored. We demonstrate this approach for Java and Groovy programs by implementing it as extensions for three popular testing frameworks (JUnit4, JUnit5 and Spock) that can transparently inject the inferred assumptions. If JUnit5 is used, those extensions can be deployed without refactoring project source code. We demonstrate and evaluate the utility of our approach using a set of six popular real-world programs, addressing known test flakiness issues in these programs caused by dependencies of tests on network availability. We find that our method effectively sanitises failures induced by network connectivity problems with high precision and recall.","PeriodicalId":138287,"journal":{"name":"2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM)","volume":"57 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126484102","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 4

To what extent can we analyze Kotlin programs using existing Java taint analysis tools? 我们可以在多大程度上使用现有的Java污染分析工具来分析Kotlin程序?

2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM) Pub Date : 2022-07-19 DOI: 10.1109/SCAM55253.2022.00032

Ranjith Krishnamurthy, Goran Piskachev, E. Bodden

引用次数: 0

首页上一页