Lines Matching full:fuzzing
3 [go/chrome-fuzzing](https://goto.google.com/chrome-fuzzing)
5 [Fuzzing] is a testing technique that feeds auto-generated inputs to a piece
8 [go/fuzzing-success](http://go/fuzzing-success)). You can learn more about the
9 benefits of fuzzing at [go/why-fuzz](http://go/why-fuzz).
11 This documentation covers the in-process guided fuzzing approach employed by
12 different fuzzing engines, such as [libFuzzer] or [AFL]. To learn more about
13 out-of-process fuzzers, please refer to the [Blackbox fuzzing] page in the
21 automatically discovered by buildbots, built with different fuzzing engines,
22 then uploaded to the distributed [ClusterFuzz] fuzzing system to run at scale.
44 * [Fuzzing mojo interfaces] using automatically generated libprotobuf-mutator fuzzers.
51 * [Fuzzing browsertests] if you need to fuzz multiple Chrome subsystems.
56 * [Bugs found in PDFium] by manual fuzzing.
60 * [Guided in-process fuzzing of Chrome components] blog post.
64 [Blackbox fuzzing]: https://google.github.io/clusterfuzz/setting-up-fuzzing/blackbox-fuzzing/
71 [Fuzzing]: https://en.wikipedia.org/wiki/Fuzzing
72 [Fuzzing browsertests]: fuzzing_browsertests.md
73 [Fuzzing mojo interfaces]: ../../mojo/docs/mojolpm.md
75 [Guided in-process fuzzing of Chrome components]: https://security.googleblog.com/2016/08/guided-in…
79 …er parts of Chrome OS]: https://chromium.googlesource.com/chromiumos/docs/+/main/testing/fuzzing.md
82 [go/fuzzing-success]: https://goto.google.com/fuzzing-success