arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2210.12155cs.SEcs.FL
收藏

在Android中对Android Enforcers进行非功能测试

Non-Functional Testing of Runtime Enforcers in Android

Oliviero Riganelli, Daniela Micucci, Leonardo Mariani

摘要:

可使用安全执行器来确保运行的应用程序满足所需的正确性属性。虽然相对于抽象行为模型,通过构造而正确的运行时执行器相对容易指定,但是从这些规范生成的具体软件执行器可能容易在目标应用中引入问题。事实上,开发人员可以生成测试套件来验证执行者的功能行为,例如利用用于指定它们的相同模型。然而,它仍然是具有挑战性和繁琐的非功能性的性能特征方面来验证执行器的行为。本文描述了一种实用的方法来揭示可能在目标应用程序中引入低效率的运行时执行器。该方法依赖于自动测试生成和多个关键性能指标的运行时监控的组合。我们设计了我们的方法来揭示移动系统的四个指标:响应能力,启动时间,内存和能耗。实验结果表明,我们的方法可以检测性能问题,可能会引入自动生成的执行器。

英文摘要:

Runtime enforcers can be used to ensure that running applications satisfy desired correctness properties. Although runtime enforcers that are correct-by-construction with respect to abstract behavioral models are relatively easy to specify, the concrete software enforcers generated from these specifications may easily introduce issues in the target application. Indeed developers can generate test suites to verify the functional behavior of the enforcers, for instance exploiting the same models used to specify them. However, it remains challenging and tedious to verify the behavior of enforcers in terms of non-functional performance characteristics. This paper describes a practical approach to reveal runtime enforcers that may introduce inefficiencies in the target application. The approach relies on a combination of automatic test generation and runtime monitoring of multiple key performance indicators. We designed our approach to reveal issues in four indicators for mobile systems: responsiveness, launch time, memory, and energy consumption. Experimental results show that our approach can detect performance issues that might be introduced by automatically generated enforcers.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑