AI 中文总结
本研究通过对比GitHub上的VRT-PR与Visual PR，分析VRT失败时开发者的讨论内容，明确VRT除样式检查外还可检测代码变更的非预期后果，为VRT工具链集成提供依据。
AI 中文摘要
视觉回归测试（Visual Regression Tests，VRT）被广泛采用为检测用户界面中非预期视觉变更的机制，其设计基于渲染后的像素输出，主流假设是它能捕捉布局偏移、颜色不匹配、字体变更等样式退化问题。我们对来自103个GitHub仓库的307个纳入Chromatic VRT结果的拉取请求（PR）开展实证分析，并将其与299个包含图片附件但无VRT的拉取请求（Visual PR）进行对比。量化结果显示，VRT-PR的接受率无显著差异，但其中位解决时间是Visual PR的3.8倍，讨论评论数是其10倍，代码变更量为其1.75至4.5倍。VRT结果通常在审查过程的中点左右被分享，用于维持持续讨论，而非仅作为最终检查。通过对189个VRT标记问题的卡片分类分析，我们确定了7类缺陷：布局（39.7%）、外观（27.5%）、颜色（14.8%）、文本（9.5%）、状态（6.9%）、测试（6.3%）、图片（4.2%）。其中三类最常见的属于样式类，约18.5%的分析问题（35/189）涉及非样式类起源，包括未定义组件状态（13例）、内容消失（跨类别共17例）、视觉不可感知的退化（5例）。我们还记录了VRT检测到源自看似无关文件的代码变更所导致的视觉退化的案例，揭示了非局部效应，这类效应是任何针对性测试都不会编写代码去捕捉的。这些观察表明，除了作为样式检查器的主要作用外，VRT还可作为代码变更非预期后果的二级检测器，这对VRT应如何集成到维护工具链中具有启示意义。
英文摘要
Visual Regression Tests (VRTs) are widely adopted as a mechanism for detecting unintended visual changes in user interfaces. By design, VRTs operate on rendered pixel output, and the prevailing assumption is that they catch stylistic regressions such as layout shifts, color mismatches, and font alterations. We conduct an empirical analysis of 307 pull requests (PRs) from 103 GitHub repositories that incorporate VRT results via Chromatic, comparing them against 299 PRs that contain image attachments but no VRT (Visual PRs). Quantitatively, VRT-PRs show no significant acceptance-rate difference, but exhibit a 3.8 times longer median resolution time, 10 times more discussion comments, and 1.75 to 4.5 times larger code changes than Visual PRs. VRT results are typically shared around the midpoint of the review process, sustaining ongoing discussion rather than serving only as a final check. Through a card-sorting analysis of 189 VRT-flagged issues, we identify seven defect categories assigned to the analyzed issues: Layout (39.7\%), Appearance (27.5\%), Color (14.8\%), Text (9.5\%), State (6.9\%), Test (6.3\%), and Image (4.2\%). The three most frequent categories are stylistic, while approximately 18.5\% of analyzed issues (35/189) involve non-stylistic origins, including undefined component state (13 cases), content disappearance (17 cases across multiple categories), and visually imperceptible regressions (5 cases). We further document cases in which VRT detected visual regressions originating from code changes in seemingly unrelated files, exposing non-local effects that no targeted test would have been written to catch. These observations indicate that, in addition to its primary role as a stylistic checker, VRT functions as a secondary detector of unintended consequences of code changes, with implications for how VRT should be integrated into the maintenance toolchain.
Comments6 pages, 1 figure, 3 tables
