-
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
Tracking: Testing the Entire Chain #745
Comments
I think our code will be simpler if we don't add any additional modes beyond what we absolutely need. |
I'd like to test the block verifier against all the blocks in the chain, to make sure we've covered any historical edge cases. What's the best way to do that? I could delete some of the hard-coded checkpoints, but that might cause issues with pre-Sapling blocks. |
We've moved all of the remaining sub-tasks out of the first alpha release, so this ticket can move to the first stable release. |
Converting any "Epics" that do not have a start and end date into github tracking issues instead. |
All these tasks are unlikely to be done any time soon. |
Goals
Make sure that
zebrad
's sync, verify, and state handling work after every commit.Check historical edge-case handling in our verifiers, by running the entire chain through them.
These basic tests are easy to automate, and provide reasonable assurance that our implementation works.
Issues from Epic
block::tests::generate
as proptest strategies. #919checkpoint/tests.rs
tests inzebra-consensus
to usezebra_test::Transcript
#744Original list
High Priority - Early Releases
Implementation
Fix Bugs That Impact Tests
Chain Testing
Re-enable the CheckpointVerifier tests Re-enable CheckpointVerifier multi-block tests #1285
Add mainnet and testnet block test vectors for each network upgrade (Test blocks #1096)
Find existing tests that use block test vectors, and see if they can use
zebra_test::vectors::TEST_BLOCKS
insteadSync Testing
Failure Testing
Automation
Lower Priority - Later Releases
Design and Scope
Fix Bugs That Impact Tests
Chain Testing
Sync Testing
zcashd
testnet instances to improve testnet reliability (Deploy more Zebra or zcashd instances on testnet #1222)zebrad
can serve blocks (HandleFindBlocks
in the Inbound service #1078), replace somezcashd
instances withzebrad
?Failure Testing
The text was updated successfully, but these errors were encountered: