-
Notifications
You must be signed in to change notification settings - Fork 56
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
Expectation tests #974
Expectation tests #974
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent. Thank you for getting to this. I would also be open to doing this for constraint and variable counts in circuits, as long as we have the appropriate guardrails and continue to orient to those as values whose changes should only be intentional and noted with close attention.
* Expectation tests for eval * Expectation test for nova * clippy --------- Co-authored-by: Gabriel Barreto <gabriel.aquino.barreto@gmail.com>
* Simplified `Func` and `Cproc` call (#966) * Expectation tests (#974) * Expectation tests for eval * Expectation test for nova * clippy --------- Co-authored-by: Gabriel Barreto <gabriel.aquino.barreto@gmail.com> * use expect_test to make assertions about circuit properties (#978) * Fix version (#977) * chore: Release * update README --------- Co-authored-by: François Garillot <francois@garillot.net> * Cleanup before patch release (#984) * chore: remove peekmore - Removed `peekmore` dependency from the project * refactor: (automated) Refactor of code for readability and style improvements - Modified the project-level lints in `.cargo/config`, added more lints enhance maintainability. - corrected the code in function, mostly through clippy. * chore: Release --------- Co-authored-by: Gabriel Barreto <gabriel.aquino.barreto@gmail.com> Co-authored-by: Arthur Paulino <arthurleonardo.ap@gmail.com>
This PR adapts the expected iterations on our evaluation and proving tests to use expect_test, which automatically updates the expected values if
cargo test
is called withUPDATE_EXPECT=1
.It was implemented in a way that prevents the auto-update if the computed iterations is greater than the expected iterations, making it easier for us to maintain a model that is not supposed to become slower.