paperbot · PL 论文追踪

全部论文 待读 收藏

P2 BigFuzz

BigFuzz
ASE Proceedings of the 35th IEEE/ACM International Conference on Automated Software Engineering2020匹配度 1/10 · 该论文属于面向大数据分析系统(如 Spark)的模糊测试/动态测试,与用户关注的静态分析、浮点程序分析、贝叶斯程序分析以及 LLM/Agent 与程序分析的交叉均无直接关联。引用 28 inbox
Qian Zhang, Jiyuan Wang, Muhammad Ali Gulzar, Rohan Padhye, Miryung Kim
crossref: 2026-09-12

AI 速览

一句话:提出 BigFuzz,将模糊测试应用于大数据分析,以应对 DISC 系统环境启动慢、覆盖率扩展难和变异数据无意义三大障碍。

随着大数据分析日益流行,数据密集型可扩展计算(DISC)系统用于处理大规模数据,但针对此类数据应用的自动化测试十分困难:数据往往不完整、持续演化且难以预先知晓。将传统模糊测试直接用于大数据分析并不简单,原因有三:DISC 系统延迟高,朴素模糊测试会把 98% 的时间花在环境搭建上;传统分支覆盖率难以扩展到 DISC 应用,因为多数二进制代码来自 Apache Spark 等框架实现;随机比特或字节级变异很难生成有意义的数据,因而无法揭示真实应用缺陷。论文提出 BigFuzz,目标是在这一场景中实现有效模糊测试,但摘要未报告其具体方法细节与实验结果。

问题
如何将模糊测试有效应用于数据密集型可扩展计算(DISC)上的大数据分析应用,克服环境搭建开销、覆盖率扩展和输入变异三大障碍。
方法
摘要未给出 BigFuzz 的具体方法细节,仅指出直接套用传统模糊测试存在环境启动慢、分支覆盖率不适用和随机变异无意义的问题。
评估
摘要未提供实验评估信息,因此无法从摘要概括评估方式与结果。
原文摘要(Abstract)

As big data analytics become increasingly popular, data-intensive scalable computing (DISC) systems help address the scalability issue of handling large data. However, automated testing for such data-centric applications is challenging, because data is often incomplete, continuously evolving, and hard to know a priori. Fuzz testing has been proven to be highly effective in other domains such as security; however, it is nontrivial to apply such traditional fuzzing to big data analytics directly for three reasons: (1) the long latency of DISC systems prohibits the applicability of fuzzing: naïve fuzzing would spend 98% of the time in setting up a test environment; (2) conventional branch coverage is unlikely to scale to DISC applications because most binary code comes from the framework implementation such as Apache Spark; and (3) random bit or byte level mutations can hardly generate meaningful data, which fails to reveal real-world application bugs.

链接与引用

DOI 原文 · PDF(开放获取) ·

BibTeX
@inproceedings{paperbot5946,
  title = {BigFuzz},
  author = {Qian Zhang and Jiyuan Wang and Muhammad Ali Gulzar and Rohan Padhye and Miryung Kim},
  booktitle = {ASE},
  year = {2020},
  doi = {10.1145/3324884.3416641}
}