From c656265d8fc65e39655168faf00d9797ff6a4164 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Wed, 4 May 2022 12:21:42 +0200 Subject: docs: say that fuzzer input samples should have short names --- docs/ARCHITECTURE.md | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs/ARCHITECTURE.md') diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index 3b81d8f737..55891a92b6 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -91,6 +91,17 @@ and generally safe to run on the host without side effects. Ideally, every module in `src/basic/` and `src/shared/` should have a corresponding unit test under `src/test/`, exercising every helper function. +## Fuzzer test cases + +Files under `test/fuzz/` contain input data for fuzzers, one subdirectory for +each fuzzer. Some of the files are "seed corpora", i.e. files that contain +lists of settings and input values intended to generate initial coverage, and +other files are samples saved by the fuzzing engines when they find an issue. + +When adding new input samples under `test/fuzz/*/`, please use some +short-but-meaningful names. Names of meson tests include the input file name +and output looks awkward if they are too long. + # Integration Tests Sources in `test/` implement system-level testing for executables, libraries and -- cgit v1.2.3