Repository navigation
docs: clarify fuzz testing guidance - #27198
Merged
Merged
Conversation
github-actions
Bot
added
the
documentation
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## main #27198 +/- ##
==========================================
+ Coverage 83.31% 83.32% +0.01%
==========================================
Files 1173 1172 -1
Lines 477463 478689 +1226
Branches 477463 478689 +1226
==========================================
+ Hits 397797 398885 +1088
- Misses 55384 55409 +25
- Partials 24282 24395 +113 see 48 files with indirect coverage changes 🚀 New features to boost your workflow:
|
alamb
approved these changes
Nov 7, 2026
| For fuzzing unit tests, such as tests for a single operator or an internal utility: | ||
|
|
||
| - If the test is small (easy to set up and takes a few seconds), keep it as a unit test. | ||
| - If the test is large (requires a fuzzing driver and takes more than 10 seconds), it must implement the [`FuzzTest` trait][fuzz framework] and run through the [central fuzz-test entry point]. See the [spill-pool fuzzer] for a reference implementation. |
Contributor
There was a problem hiding this comment.
Do we want to make it a "must" ? Perhaps it would be better as an advisory ("should")?
2010YOUY01
commented
Nov 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 8, 2026
1 of 31 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Fork CI setup: For pull requests from a fork to
main, enable workflows in your fork's Actions tab before you push.See the fork CI setup guide.
Which issue does this PR close?
part of #27082
Follow up: #27048
Rationale for this change
#27048 introduced a trait for implementing fuzzing UTs, this PR adds documentation for it.
What changes are included in this PR?
What is the testing strategy for this PR?
Are there any user-facing changes?