Lines Matching +full:report +full:- +full:coverage

1 # Code Coverage
3 Code coverage can be checked using clang's source-based coverage tools.  You
10 pre-built clang coverage tools, which are not downloaded by default.  The
21 ([link](https://storage.googleapis.com/chromium-browser-clang-staging/)).
23 Once you have your GN directory (we'll call it `out/coverage`) and have
24 downloaded the tools, do the following to generate an HTML coverage report:
26 out/coverage/openscreen_unittests
27 third_party/llvm-build/Release+Asserts/bin/llvm-profdata merge -sparse default.profraw -o foo.profd…
28 …ird_party/llvm-build/Release+Asserts/bin/llvm-cov show out/coverage/openscreen_unittests -instr-pr…
31  - `default.profraw` is generated by running the instrumented code, but
33  - `<out dir>` should be an empty directory for placing the generated HTML
34  files.  You can view the report at `<out dir>/index.html`.
35  - `[filter paths]` is a list of paths to which you want to limit the coverage
36  report.  For example, you may want to limit it to cast/ or even
37  cast/streaming/.  If this list is empty, all data will be in the report.
39 The same process can be used to check the coverage of a fuzzer's corpus.  Just
40 add `-runs=0` to the fuzzer arguments to make sure it only runs the existing