Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[enhancement] Exhaustive quickchecks #1715

Closed
grebe opened this issue Nov 14, 2024 · 0 comments · Fixed by #1829
Closed

[enhancement] Exhaustive quickchecks #1715

grebe opened this issue Nov 14, 2024 · 0 comments · Fixed by #1829
Assignees
Labels
enhancement New feature or request

Comments

@grebe
Copy link
Collaborator

grebe commented Nov 14, 2024

What's hard to do? (limit 100 words)

If the input domain of a quickcheck is small enough, it's natural to want to check exhaustively. It appears that interpreter_main doesn't enforce that each test case is novel, so you can't choose test_count=LARGE_NUMBER st the test is guaranteed to be exhaustive. Even if you could choose LARGE_NUMBER s.t. it would be exhaustive, changing a type of some input could make it too small later, and keeping those up to date seems hard.

Something like quickcheck(exhaustive) would be nice.

Current best alternative workaround (limit 100 words)

Choose a very large test_count. Use a prove quickcheck target so Z3 proves the property.

Your view of the "best case XLS enhancement" (limit 100 words)

Some annotation that you want the property to be checked exhaustively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants