Merge pull request #526 from crytic/dev/explore-flag

Add exploration mode flag

Author: bsamuels453

cmd/fuzz_flags.go

@@ -63,6 +63,9 @@ func addFuzzFlags() error {
 	// Logging color
 	fuzzCmd.Flags().Bool("no-color", false, "disabled colored terminal output")
 
+	// Exploration mode
+	fuzzCmd.Flags().Bool("explore", false, "enables exploration mode")
+
 	return nil
 }
 
@@ -163,5 +166,20 @@ func updateProjectConfigWithFuzzFlags(cmd *cobra.Command, projectConfig *config.
 			return err
 		}
 	}
+
+	// Update configuration to exploration mode
+	if cmd.Flags().Changed("explore") {
+		exploreBool, err := cmd.Flags().GetBool("explore")
+		if err != nil {
+			return err
+		}
+		if exploreBool {
+			projectConfig.Fuzzing.Testing.StopOnFailedTest = false
+			projectConfig.Fuzzing.Testing.StopOnNoTests = false
+			projectConfig.Fuzzing.Testing.AssertionTesting.Enabled = false
+			projectConfig.Fuzzing.Testing.PropertyTesting.Enabled = false
+			projectConfig.Fuzzing.Testing.OptimizationTesting.Enabled = false
+		}
+	}
 	return nil
 }

docs/src/cli/fuzz.md

@@ -129,3 +129,12 @@ The `--no-color` flag disables colored console output (equivalent to
 # Disable colored output
 medusa fuzz --no-color
 ```
+
+### `--explore`
+
+The `--explore` flag enables exploration mode. This sets the [`StopOnFailedTest`](../project_configuration/testing_config.md#stoponfailedtest) and [`StopOnNoTests`](../project_configuration/testing_config.md#stoponnotests) fields to `false` and turns off assertion, property, and optimization testing.
+
+```shell
+# Enable exploration mode
+medusa fuzz --explore
+```