-
Notifications
You must be signed in to change notification settings - Fork 159
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
web3.eth.account signature hypothesis tests #107
Comments
We can use the same strategy that we used to speed up the test suite in the Py-EVM codebase for slow tests like this. We can setup a daily cron run on travis that runs and only run the slow tests during the cron run. See implementation here: https://github.com/ethereum/py-evm/blob/master/tests/json-fixtures/test_state.py#L116-L119 |
[old issue cleanup] I believe this hypothesis testing belongs (and already exists) in eth-account. Correct me if I'm wrong. |
Hm, I don't think this particular test exists yet in eth-account. Maybe copy/move the issue over and reopen? |
Re: transfer, looks like I've got insufficient privileges in eth-account @carver. Would you mind moving it over? (The |
@marcgarreau Transferred! TIL ✨ |
What was wrong?
Want to catch/prevent more issues like ethereum/web3.py#466 earlier.
How can it be fixed?
More hypothesis tests. Piper's suggestions (on ethereum/web3.py#477):
The downside is that they can be pretty time-intensive. Just a test for the length of signature bytes added 7 seconds to a 53-second test suite.
Example:
The text was updated successfully, but these errors were encountered: