You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reading the rust book again, I realized that it recommends that integration test be put in their own directory, rather than the status quo where they are in main.rs
Eventually we'll get many many more integration tests, for all the possible branches. For example the case where a taker sends money into a coinswap address but the maker becomes unresponsive, forcing the taker to broadcast its own contract transaction and wait for the timeout to get its money back.
This helps in creating multiple bitcoind backend and connect them together and create our own regtest network. I am not sure if it will be super helpful in our test scenarios. But if we need to have multiple core nodes into the test environment, that might come handy.
Multiple bitcoind instances connected together are not that useful for us. If needed it's possible to simulate blockchain reorgs using invalidateblock and reconsiderblock.
While reading the rust book again, I realized that it recommends that integration test be put in their own directory, rather than the status quo where they are in
main.rs
https://doc.rust-lang.org/book/ch11-03-test-organization.html#integration-tests
The text was updated successfully, but these errors were encountered: