Closed
Description
Description
We want to detect non-deterministic behavior in user's code such as Random calls and others while executing it by Concrete Executor.
Cases:
- fuzzing
- executing in the middle of symbolic analyzing
There is an issue with a brief description of such a problem in fuzzing #1135
Expected behavior
We should generate tests having deterministic behavior.
Environment
A clear example of this is described in issue #1135
Potential alternatives
We can run user's code several times to understand there is non-deterministic behavior or not.
Context
Classes with non-deterministic behavior:
- Random:
- java.util.Random
- java.security.SecureRandom
- java.util.concurrent.ThreadLocalRandom
- Any file reading?
- Any networking?
Metadata
Metadata
Assignees
Type
Projects
Status