-
Notifications
You must be signed in to change notification settings - Fork 30
CSV output
Duy Tai Nguyen edited this page Jun 28, 2019
·
1 revision
| Name | Description |
|---|---|
| duration | The execution time of current process |
| execution | The number of executed test cases during theduration
|
| speed | The speed of fuzzer = duration / excution
|
| cycle | Fuzzer keeps all interesting test cases in a queue, it picks the interesting test case one by one and move from the beginning to the end of the queue. The cycle is increased by 1 if the fuzzer traverses all interesting test cases in the queue and jumps to the beginning of the queue |
| visited_pcs | The number of visited opcodes |
| exception type | The number of exception categories recorded in the current contract. An exception type is one in the list: BadInstruction, BadJumpDestination, OutOfGas, OutOfStack, StackUnderflow, DisallowedStateChange, BufferOverrun, etc. |
| exception | The number of exceptions occur in the current contract |
<Stage_Name>-tuple |
The number of interesting test cases discovered in the stage <Stage_Name> |
<Stage_Name>-exec |
The number of executed test cases in the stage <Stage_Name> |
| max depth | The depth of interesting test case T is d , if the fuzzer discovers a new interesting test case T1 from T then the depth of T1 = d + 1. Max depth is the maximum depth value of all interesting test cases |
| gasless, disorder, reentrancy, timestamp, number, delegate, freezing, overflow, underflow |
1 means found, 0 is not found |
| branches | The number of covered branches |
| coverage | Branch coverage |
| predicates, callorder, tuple | The meaning is not clear |
- Interesting test case: the test case covers new branch or satisfy the objective function of the fuzzer
-
<Stage_Name>: the name of the mutation stage