Fuzzing can experience saturation where the number of new bugs found by a fuzzer drops off over time, either due to the bugs being triggered at low probability or because some bugs are out of reach for the fuzzer. Saturation can be detected using coverage-based stopping criteria or by splitting a testing effort into subsets
Table of contents
Detecting SaturationSaturation in Practice: Fuzzing a Smart Contract CompilerMitigating SaturationSort: