From c720e4046bb32fbf2a4b76dd226874a3490efde5 Mon Sep 17 00:00:00 2001 From: Max Moroz Date: Tue, 17 Jul 2018 12:34:25 -0700 Subject: [PATCH] [docs] Link code_coverage.md page from the ideal_integration.md. (#1621) --- docs/ideal_integration.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/ideal_integration.md b/docs/ideal_integration.md index 728c9af8a..6c5a2f1a0 100644 --- a/docs/ideal_integration.md +++ b/docs/ideal_integration.md @@ -104,6 +104,10 @@ For a fuzz target to be useful, it must have good coverage in the code that it i for your fuzz targets by looking at the [fuzzer stats](https://github.com/google/oss-fuzz/blob/master/docs/clusterfuzz.md#fuzzer-stats) dashboard on ClusterFuzz, as well as [coverage reports](https://github.com/google/oss-fuzz/blob/master/docs/clusterfuzz.md#coverage-reports). +To generate an aggregated code coverage report for your project, please see +[code coverage](https://github.com/google/oss-fuzz/blob/master/docs/code_coverage.md) +documentation page. + Coverage can often be improved by adding dictionaries, more inputs for seed corpora, and fixing timeouts/out-of-memory bugs in your targets.