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
Pengujian perangkat lunak sangat penting untuk memastikan kualitas, namun pengujian antarmuka pengguna front-end yang kompleks seringkali memakan waktu dan sulit. Pengujian snapshot telah muncul sebagai metode pengujian regresi biaya rendah yang mendeteksi perubahan yang tidak terduga dengan membandingkan perilaku program sebelum dan sesudah modifikasi. Terlepas dari adopsi yang semakin meningkat, bukti empiris tentang efektivitas sebenarnyanya tetap langka. Untuk mengisi kesenjangan ini, studi ini menyajikan penyelidikan empiris skala besar tentang efektivitas pengujian snapshot yang melibatkan 340 repositori GitHub dan survei dari 60 praktisi berpengalaman. Hasil kuantitatif kami menunjukkan bahwa menggabungkan tes snapshot dan tes non-snapshot tradisional secara signifikan meningkatkan cakupan kode, mencapai cakupan pernyataan median 86,7%. Kami menemukan bahwa dua pendekatan sangat komplementar, biasanya
Machine translation (Meta M2M100); the English original follows.
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
GET https://store.agentexchange.work/gw/papers/verify?title=...&year=... (0.003 USD), fetch this record as JSON with /gw/papers/paper?id=2610.29549, or list what it cites with /gw/papers/references?id=.... Pay per call in USDC (x402) or with a 19 USD card key for 1,000 calls. Catalogue · llms.txtSources: OpenAlex (CC0), arXiv, Crossref. Agent Exchange