Fix try-runtime follow-chain, try-runtime upgrade tuple tests, cli test utils#13794
Fix try-runtime follow-chain, try-runtime upgrade tuple tests, cli test utils#13794liamaharon merged 31 commits intomasterfrom
try-runtime follow-chain, try-runtime upgrade tuple tests, cli test utils#13794Conversation
kianenigma
left a comment
There was a problem hiding this comment.
New tests to prevent this happening again?
|
Hey @kianenigma, I've added a test for The test
Misc extra notes/questions about the changes:
|
try-runtime follow-chain, add pre/post runtime upgrade tuple testtry-runtime follow-chain, try-runtime upgrade tuple tests, cli test utils
…x-try-runtime-follow-chain
…x-try-runtime-follow-chain
| use tokio::process::{Child, Command}; | ||
|
|
||
| #[tokio::test] | ||
| async fn follow_chain_works() { |
There was a problem hiding this comment.
now that we have the infra, should we make tests for all commands? can be an issue that you either do yourself, or mentor.
There was a problem hiding this comment.
Yes, I think we should have tests for subcommands too; otherwise they'll just accidentally break sooner or later.
There was a problem hiding this comment.
Absolutely, it's tracked in this issue: #13796. I wanted to test just one command and get the approach reviewed before adding tests for the rest of them.
There're issues reported with some of the other try-runtime commands that I'm close to getting started on, I'll utilise this test infra while debugging those and leave the tests in the fix PR.
kianenigma
left a comment
There was a problem hiding this comment.
LGTM, but would be good if someone from @paritytech/sdk-node also takes a look 👍
Co-authored-by: Koute <koute@users.noreply.github.com>
…test utils (paritytech#13794) * new test for try-runtime tuple stuff * fix * remove development comment * formatting * remove todo comment * follow-chain working test * refactor common cli testing utils * fix comment * revert Cargo.lock changes * update Cargo.lock * improve doc comment * fix error typo * update Cargo.lock * feature gate try-runtime test * build_substrate cli test util * feature gate follow_chain tests * move fn start_node to test-utils * improve test pkg name * use tokio Child and Command * remove redundant import * fix ci * fix ci * don't leave hanging processes * improved child process cleanup * use existing KillChildOnDrop * remove redundant comment * Update test-utils/cli/src/lib.rs Co-authored-by: Koute <koute@users.noreply.github.com> --------- Co-authored-by: kianenigma <kian@parity.io> Co-authored-by: Koute <koute@users.noreply.github.com>
…test utils (paritytech#13794) * new test for try-runtime tuple stuff * fix * remove development comment * formatting * remove todo comment * follow-chain working test * refactor common cli testing utils * fix comment * revert Cargo.lock changes * update Cargo.lock * improve doc comment * fix error typo * update Cargo.lock * feature gate try-runtime test * build_substrate cli test util * feature gate follow_chain tests * move fn start_node to test-utils * improve test pkg name * use tokio Child and Command * remove redundant import * fix ci * fix ci * don't leave hanging processes * improved child process cleanup * use existing KillChildOnDrop * remove redundant comment * Update test-utils/cli/src/lib.rs Co-authored-by: Koute <koute@users.noreply.github.com> --------- Co-authored-by: kianenigma <kian@parity.io> Co-authored-by: Koute <koute@users.noreply.github.com>
…test utils (#13794) * new test for try-runtime tuple stuff * fix * remove development comment * formatting * remove todo comment * follow-chain working test * refactor common cli testing utils * fix comment * revert Cargo.lock changes * update Cargo.lock * improve doc comment * fix error typo * update Cargo.lock * feature gate try-runtime test * build_substrate cli test util * feature gate follow_chain tests * move fn start_node to test-utils * improve test pkg name * use tokio Child and Command * remove redundant import * fix ci * fix ci * don't leave hanging processes * improved child process cleanup * use existing KillChildOnDrop * remove redundant comment * Update test-utils/cli/src/lib.rs Co-authored-by: Koute <koute@users.noreply.github.com> --------- Co-authored-by: kianenigma <kian@parity.io> Co-authored-by: Koute <koute@users.noreply.github.com>
|
This pull request has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/april-updates-for-substrate-and-polkadot-devs/2764/1 |
…test utils (paritytech#13794) * new test for try-runtime tuple stuff * fix * remove development comment * formatting * remove todo comment * follow-chain working test * refactor common cli testing utils * fix comment * revert Cargo.lock changes * update Cargo.lock * improve doc comment * fix error typo * update Cargo.lock * feature gate try-runtime test * build_substrate cli test util * feature gate follow_chain tests * move fn start_node to test-utils * improve test pkg name * use tokio Child and Command * remove redundant import * fix ci * fix ci * don't leave hanging processes * improved child process cleanup * use existing KillChildOnDrop * remove redundant comment * Update test-utils/cli/src/lib.rs Co-authored-by: Koute <koute@users.noreply.github.com> --------- Co-authored-by: kianenigma <kian@parity.io> Co-authored-by: Koute <koute@users.noreply.github.com>
folllow-chainbug (closes try-runtime follow-chain seems broken #13696)follow-chaintest (related try-runtime-cli docs and tests #13796)pre_upgradeandpost_upgradehooks are executed correctly for tuple migrations (related: try-runtime pre-post hooks not executed if defined within the pallet #13681)