Fuzz test target #866

New issue

Open

opened 2025-12-28 17:14:30 +00:00 by sami · 2 comments

sami commented

2025-12-28 17:14:30 +00:00

Owner

Originally created by @roman-khimov on GitHub (Feb 28, 2022).

Go 1.18 can fuzz our code out of the box, we need to figure out how to make use of and try adding some make targets. Most likely it can't be a part of regular CI builds though.

Originally created by @roman-khimov on GitHub (Feb 28, 2022). Go 1.18 can [fuzz our code](https://go.dev/doc/fuzz) out of the box, we need to figure out how to make use of and try adding some make targets. Most likely it can't be a part of regular CI builds though.

sami added the

feature

labels

2025-12-28 17:14:30 +00:00

sami commented

2025-12-28 17:14:30 +00:00

Author

Owner

@roman-khimov commented on GitHub (Mar 18, 2022):

@fyrchik, I think we should add fuzz tests for #2396 and #2397. Eventually we'll have more of them.

@roman-khimov commented on GitHub (Mar 18, 2022): @fyrchik, I think we should add fuzz tests for #2396 and #2397. Eventually we'll have more of them.

sami commented

2025-12-28 17:14:30 +00:00

Author

Owner

@roman-khimov commented on GitHub (Jun 9, 2022):

Keeping this as a reminder. In general we want to have a fuzzing test at least for all input data we have (network payloads of various sorts mostly). I'm not so sure about Makefile wrapper to run them though, go doesn't make it very convenient.

@roman-khimov commented on GitHub (Jun 9, 2022): Keeping this as a reminder. In general we want to have a fuzzing test at least for all input data we have (network payloads of various sorts mostly). I'm not so sure about Makefile wrapper to run them though, go doesn't make it very convenient.