Add branch exploration for Z3 test case generation #111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some performance hit here
…aramana_3d_z3_test_branch_trace
…aramana_3d_z3_test_branch_trace
…empty files reported by @lemmy
…aramana_3d_z3_test_branch_trace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces 3D options:
--z3_branch_depth nto ask z3 to generate test cases for all possible branches of a 3D specification up to depthn, by depth-first search. Default is 0, with the usual behavior. For this purpose, branching points in a 3D specification are field constraints andcasetypes.--z3_options 'option1 ... optionK'to pass command-line options to z3, such as-t:xto impose a per-query timeout ofxmilliseconds