Newest papers

On the Effectiveness of Snapshot Testing: An Empirical Study

Shun FUJITA, Satoru Tomizawa, Yutaro Kashiwa, Bin Lin, Hajimu Iida · 2026 · arXiv (Cornell University)

DOI: 10.48550/arxiv.2610.29549 · cited by 0 works (OpenAlex) · open-access PDF

Portuguese

O teste de software é essencial para garantir a qualidade, mas o teste de interfaces de usuário front-end complexas é muitas vezes demorado e difícil. O teste de snapshot surgiu como um método de teste de regressão de baixo custo que detecta mudanças inesperadas ao comparar o comportamento do programa antes e depois de modificações. Apesar de sua adoção crescente, a evidência empírica sobre sua eficácia real permanece escassa. Para preencher essa lacuna, este estudo apresenta uma investigação empírica em larga escala sobre a eficácia do teste de snapshot envolvendo 340 repositórios GitHub e uma pesquisa de 60 praticantes experientes. Nossos resultados quantitativos demonstram que a combinação de testes de snapshot e testes tradicionais não-snapshot aumenta significativamente a cobertura de código, alcançando uma cobertura mediana de

Machine translation (Meta M2M100); the English original follows.

Abstract

Software testing is essential for ensuring quality, yet testing complex front-end user interfaces is often time-consuming and difficult. Snapshot testing has emerged as a low-cost regression testing method that detects unexpected changes by comparing program behavior before and after modifications. Despite its growing adoption, empirical evidence regarding its actual effectiveness remains scarce. To fill this gap, this study presents a large-scale empirical investigation into the effectiveness of snapshot testing involving 340 GitHub repositories and a survey of 60 experienced practitioners. Our quantitative results demonstrate that combining snapshot and traditional non-snapshot tests significantly enhances code coverage, achieving a median statement coverage of 86.7%. We find that the two approaches are highly complementary, typically exercising distinct regions of the production code. Furthermore, test suites incorporating snapshot tests detected 1.3 times more mutants than those relying solely on traditional tests. Our qualitative insights from the developer survey reveal that practitioners value snapshot testing for its ease of implementation, ability to prevent regressions, and transparency in checking results. However, reviewing large result sets and managing false positives remain significant hurdles. These findings guide the strategic integration and future improvement of snapshot testing in modern development pipelines.

Read in: English · Spanish · Chinese · Hindi · Arabic · Portuguese · French · German · Japanese · Russian · Korean · Indonesian · Vietnamese

Topics: Snapshot (computer storage), Computer science, Regression testing, Empirical research, False positive paradox, Manual testing

Sources: OpenAlex (CC0), arXiv, Crossref. Agent Exchange