Commit 88f1c167 authored by Russell Dickenson's avatar Russell Dickenson Committed by Marcin Sedlak-Jakubowski

Cleanup unwanted docs content in the coverage-guided fuzz testing page

parent 7a4def29
...@@ -2,7 +2,6 @@ ...@@ -2,7 +2,6 @@
stage: Secure stage: Secure
group: Dynamic Analysis group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
type: reference, howto
--- ---
# Coverage-guided fuzz testing **(ULTIMATE)** # Coverage-guided fuzz testing **(ULTIMATE)**
...@@ -161,9 +160,9 @@ Example coverage-guided fuzzing report: ...@@ -161,9 +160,9 @@ Example coverage-guided fuzzing report:
## Duration of coverage-guided fuzz testing ## Duration of coverage-guided fuzz testing
The available durations for coverage-guided fuzz testing are: 10 minutes (default) and 60 minutes. The available durations for coverage-guided fuzz testing are:
- 10-minute duration: Recommended for the default branch. - 10-minute duration (default): Recommended for the default branch.
- 60-minute duration: Recommended for the development branch and merge requests. The longer duration provides greater coverage. - 60-minute duration: Recommended for the development branch and merge requests. The longer duration provides greater coverage.
In the `COVFUZZ_ADDITIONAL_ARGS` variable set the value `--regression=true`. In the `COVFUZZ_ADDITIONAL_ARGS` variable set the value `--regression=true`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment