diff options
| author | jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com> | 2021-01-25 08:41:34 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-01-25 08:41:34 -0800 |
| commit | 0ac841a1a40c7ef9def6b65834cf823c7f298e23 (patch) | |
| tree | 8d94affc84904315895c31813ad6d7179f6bee9f /docs/getting-started/new_project_guide.md | |
| parent | 20b7246eae02785153ada2ae3dad97a546c7f589 (diff) | |
| download | oss-fuzz-0ac841a1a40c7ef9def6b65834cf823c7f298e23.tar.gz | |
Replace terms that are uninclusive. (#5045)
Diffstat (limited to 'docs/getting-started/new_project_guide.md')
| -rw-r--r-- | docs/getting-started/new_project_guide.md | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md index 71a886aa7..3d113c9c4 100644 --- a/docs/getting-started/new_project_guide.md +++ b/docs/getting-started/new_project_guide.md @@ -39,7 +39,7 @@ Before you can start setting up your new project for fuzzing, you must do the fo [docker-cleanup](https://gist.github.com/mikea/d23a839cba68778d94e0302e8a2c200f) periodically to garbage-collect unused images. -- (optional) [Install gsutil](https://cloud.google.com/storage/docs/gsutil_install) for local code coverage sanity check. +- (optional) [Install gsutil](https://cloud.google.com/storage/docs/gsutil_install) for local code coverage testing. For Google internal (gLinux) machines, please refer [here](https://cloud.google.com/storage/docs/gsutil_install#deb) instead. ## Creating the file structure @@ -325,10 +325,9 @@ You can build your docker image and fuzz targets locally, so you can test them b $ python infra/helper.py run_fuzzer $PROJECT_NAME <fuzz_target> --corpus-dir=<path-to-temp-corpus-dir> ``` -4. We recommend taking a look at your code coverage as a sanity check to make -sure that your fuzz targets get to the code you expect. This would use the -corpus generated from the previous `run_fuzzer` step in your local corpus -directory. +4. We recommend taking a look at your code coverage as a test to ensure that +your fuzz targets get to the code you expect. This would use the corpus +generated from the previous `run_fuzzer` step in your local corpus directory. ```bash $ python infra/helper.py build_fuzzers --sanitizer coverage $PROJECT_NAME |