📝 Inform to change direcotry before fuzz start

Ackee-Blockchain · Jan 15, 2025 · 32f767d · 32f767d
1 parent e6554fd
commit 32f767d
Show file tree

Hide file tree

Showing 3 changed files with 30 additions and 20 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/documentation/docs/commands/commands.md b/documentation/docs/commands/commands.md
@@ -52,6 +52,9 @@ trident fuzz <subcommand>
 
 ### trident fuzz run-afl
 
+!!! warning
+    To execute and debug fuzz tests, navigate to the `trident-tests` directory.
+
 ```bash
 trident fuzz run-afl <fuzz_target>
 ```
@@ -64,6 +67,9 @@ TBD
 
 ### trident fuzz run-hfuzz
 
+!!! warning
+    To execute and debug fuzz tests, navigate to the `trident-tests` directory.
+
 ```bash
 trident fuzz run-hfuzz <fuzz_target>
 ```

diff --git a/documentation/docs/writing-fuzz-test/writing-fuzz-test.md b/documentation/docs/writing-fuzz-test/writing-fuzz-test.md
@@ -75,6 +75,9 @@ Each Instruction in the Fuzz Test must define the following functions:
 
 ## Execute
 
+!!! warning
+    To execute and debug fuzz tests, navigate to the `trident-tests` directory.
+
 ### Run Fuzz Test
 
 In principle there are two possible fuzzing engines that the Trident supports, [Honggfuzz](https://github.com/google/honggfuzz) and [AFL](https://aflplus.plus/).