We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given that proptest may need different sampling for valid vs. invalid inputs, it makes sense to handle these separately.
As discussed, we've decided to handle error cases in manual tests and only test validity in the randomized tests.
This should be updated in the processor u32 tests here
Maybe invalid cases can be handled in manual tests? And the test validity of operations over valid inputs using randomized tests?
Originally posted by @bobbinth in #75 (comment)
The text was updated successfully, but these errors were encountered:
test: remove failure cases from proptests
e45c7c9
This addresses issue 0xPolygonMiden#79 to use proptests only for validity testing and handle error cases in manual tests
Fixed by #89
Sorry, something went wrong.
grjte
No branches or pull requests
Given that proptest may need different sampling for valid vs. invalid inputs, it makes sense to handle these separately.
As discussed, we've decided to handle error cases in manual tests and only test validity in the randomized tests.
This should be updated in the processor u32 tests here
Originally posted by @bobbinth in #75 (comment)
The text was updated successfully, but these errors were encountered: