* Move mempool tests into `tests::vector` sub-module Make it consistent with other test modules and prepare for adding property tests. * Reorder imports Make it consistent with the general guidelines followed on other modules. * Export `ChainTipBlock` and `ChainTipSender` Allow these types to be used in other crates for testing purposes. * Derive `Arbitrary` for `ChainTipBlock` Make it easy to generate random `ChainTipBlock`s for usage in property tests. * Refactor to move test methods into `tests` module Reduce the repeated test configuration attributes and make it easier to see what is test specific and what is part of the general implementation. * Add a `Mempool::dummy_call` test helper method Performs a dummy call just so that `poll_ready` gets called. * Use `dummy_call` in existing tests Replace the custom dummy requests with the helper method. * Test if the mempool is cleared on chain reset A chain reset should force the mempool storage to be cleared so that transaction verification can restart using the new chain tip. * Test if mempool is cleared on syncer restart If the block synchronizer falls behind and then starts catching up again, the mempool should be disabled and therefore the storage should be cleared. |
||
---|---|---|
.. | ||
proptest-regressions/service | ||
src | ||
tests | ||
Cargo.toml | ||
build.rs |