Lines Matching +full:enable +full:- +full:integration +full:- +full:tests
1 # JUnit Integration Implementation
3 Jazzer's JUnit integration starts from
5 annotation's javadoc, our integration runs in one of two modes: fuzzing and regression. Fuzzing mod…
6 inputs to feed into the tests to find new issues and regression mode will run the tests against pre…
7 fuzzing is done. The main entrypoints for the actual integration code are found in two of the annot…
12 non-empty value) and in regression mode (when `JAZZER_FUZZ` is not set) separately.
21 be run due to global state in libfuzzer that would mean multiple tests would interfere with each ot…
47 libfuzzer are saved in `.cifuzz-corpus`.
55 This checks if the given test should be run at all. In regression mode, all tests are run so this w…
64 3. If a `.cifuzz-corpus` directory exists, relevant entries from that are added as well
69 ### Resources Tests
71 The tests from the resources directory are gathered by `walkInputs`. This will look for inputs in t…
72 - `resources/<package>/<test class name>Inputs` - files found directly within this directory will b…
73 …any tests within this class. This allows for easy sharing of corpus entries. Jazzer does not autom…
75 - `resources/<package>/<test class name>Inputs/<test method name>` - files found in this directory …
83 The corpus kept in `.cifuzz-corpus/<test class name>/<test method name>` holds any inputs that libf…
86 in `.cifuzz-corpus/<test class name>` for shared test cases. This is a limitation of libfuzzer.
96 with the provided arguments. Prior to the call to the test, it will enable the agent's hooks and th…
107 
111 