-
Notifications
You must be signed in to change notification settings - Fork 111
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
Use testnet blocks in the unit tests #683
Labels
Comments
teor2345
added
Poll::Ready
good first issue
E-help-wanted
Call for participation: Help is requested to fix this issue.
labels
Jul 20, 2020
@oxarbitrage you might be interested in doing this ticket. |
Will take it, thanks @teor2345 |
We've added the testnet blocks, but we still need to use them in more tests. |
teor2345
changed the title
Add testnet blocks to zebra-test, and use them in the tests
Use tesnet blocks in the unit tests
Nov 24, 2020
No-one is working on this ticket at the moment |
dconnolly
changed the title
Use tesnet blocks in the unit tests
Use testnet blocks in the unit tests
Dec 17, 2020
2 tasks
6 tasks
These tests either got fixed, or they are obsolete. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
At the moment, zebra-test only has mainnet test vectors.
Let's add some testnet blocks to zebra-test, and use them in the tests:
Let's use a different PR for each crate where we update the tests.
It might be helpful to have utility functions that:
It might also be helpful to re-write some of our tests to take a Network enum parameter.
The text was updated successfully, but these errors were encountered: