From 22726315c3bd31f53c2f4bcf1f8649767ec5276a Mon Sep 17 00:00:00 2001
From: llzmb <46303940+llzmb@users.noreply.github.com>
Date: Wed, 24 Nov 2021 08:11:15 +0100
Subject: Merge various files into "fuzzing_in_depth.md"

---
 docs/choosing_testcases.md | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 docs/choosing_testcases.md

(limited to 'docs/choosing_testcases.md')

diff --git a/docs/choosing_testcases.md b/docs/choosing_testcases.md
deleted file mode 100644
index 25002929..00000000
--- a/docs/choosing_testcases.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# Choosing initial test cases
-
-To operate correctly, the fuzzer requires one or more starting file that
-contains a good example of the input data normally expected by the targeted
-application. There are two basic rules:
-
-  - Keep the files small. Under 1 kB is ideal, although not strictly necessary.
-    For a discussion of why size matters, see [perf_tips.md](perf_tips.md).
-
-  - Use multiple test cases only if they are functionally different from
-    each other. There is no point in using fifty different vacation photos
-    to fuzz an image library.
-
-You can find many good examples of starting files in the testcases/ subdirectory
-that comes with this tool.
-
-PS. If a large corpus of data is available for screening, you may want to use
-the afl-cmin utility to identify a subset of functionally distinct files that
-exercise different code paths in the target binary.
\ No newline at end of file
-- 
cgit 1.4.1