敏捷与持续集成环境中回归测试的形式化
Formalizing Regression Testing for Agile and Continuous Integration Environments
AI总结：
本研究将敏捷与持续集成环境中的持续回归测试形式化为时间有序构建链与回归测试窗口，证明其可退化为经典retest-all，并通过表示两种先进算法验证了形式化的可靠性与完备性。
摘要：
使用现代敏捷实践开发的软件会交付一系列连续的软件版本，这需要持续的回归测试，而不是像经典回归测试理论所假设的那样仅在接近交付或维护阶段时测试一次。在本研究中，我们将使用连续构建的持续或近乎持续的回归测试现象形式化为一个时间有序链，其中每个构建包含程序、需求和伴随的测试。我们还形式化了任意两个构建之间的回归测试窗口，它捕获了可用于回归测试的有限时间预算。当时间限制设为无穷大且链封闭为两个构建时，模型退化为retest-all，从而保留了经典双版本情况的语义。该形式化通过直接用构建元组操作表示两种最先进的敏捷回归测试算法而无需辅助假设来验证，随后证明了我们形式化的可靠性和完备性。
英文摘要：
Software developed using modern agile practices delivers a stream of software versions that require continuous regression testing rather than testing once close to the delivery or maintenance phase, as assumed by classical regression-testing theory. In this work, we formalize the phenomenon of continuous or near-continuous regression testing using successive builds as a time-ordered chain, where each build contains the program, requirements, and the accompanying tests. We also formalize the regression test window between any two builds, which captures the limited time budget available for regression testing. As the time limit is set to infinity and the chain is closed to two builds, the model degenerates to retest-all, thereby preserving semantics for the classical two-version case. The formalization is validated by directly representing two state-of-the-art agile regression testing algorithms in terms of build-tuple operations without requiring auxiliary assumptions, followed by proof of the soundness and completeness of our formalization.
机构、总结、中文摘要均由AI分析而来，可能存在错误，请以论文正文为准。
