diff options
Diffstat (limited to 'tools/javafuzz/README.md')
| -rw-r--r-- | tools/javafuzz/README.md | 22 |
1 files changed, 18 insertions, 4 deletions
diff --git a/tools/javafuzz/README.md b/tools/javafuzz/README.md index b08075a9d8..a70e4c117f 100644 --- a/tools/javafuzz/README.md +++ b/tools/javafuzz/README.md @@ -8,7 +8,7 @@ using the optimizing compiler, using an external reference implementation, or using various target architectures. Any difference between the outputs (**divergence**) may indicate a bug in one of the execution modes. -JavaFuzz can be combined with dexfuzz to get multi-layered fuzz testing. +JavaFuzz can be combined with DexFuzz to get multi-layered fuzz testing. How to run JavaFuzz =================== @@ -36,11 +36,11 @@ a fixed testing class named Test. So a typical test run looks as follows. jack -cp ${JACK_CLASSPATH} --output-dex . Test.java art -classpath classes.dex Test -How to start the JavaFuzz tests -=============================== +How to start JavaFuzz testing +============================= run_java_fuzz_test.py - [--num_tests=#TESTS] + [--num_tests=NUM_TESTS] [--device=DEVICE] [--mode1=MODE] [--mode2=MODE] @@ -56,6 +56,20 @@ where tint = Art interpreter on target topt = Art optimizing on target +How to start Java/DexFuzz testing (multi-layered) +================================================= + + run_dex_fuzz_test.py + [--num_tests=NUM_TESTS] + [--num_inputs=NUM_INPUTS] + [--device=DEVICE] + +where + + --num_tests : number of tests to run (10000 by default) + --num_inputs: number of JavaFuzz programs to generate + --device : target device serial number (passed to adb -s) + Background ========== |