Introduce test runner biolerplate#2609
Conversation
Co-authored-by: Andronik Ordian <[email protected]>
…t into substrate-test-runner
|
@ordian @kianenigma @bkchr could you please take a look at this? |
|
every new file uses spaces instead of tabs, please fix that as well as |
damn, vscode strikes again |
| let mut tokio_runtime = build_runtime()?; | ||
| let task_executor = task_executor(tokio_runtime.handle().clone()); | ||
| // parse cli args | ||
| let cmd = <polkadot_cli::Cli as StructOpt>::from_args(); |
There was a problem hiding this comment.
nit: There should be variant of this run that allows passing the Cli args explicitly rather than expecting them to present in the environment.
There was a problem hiding this comment.
hmm, interesting but what would be the use case?
There was a problem hiding this comment.
My idea was to also use this for small scale integration test level networks, launching 3 nodes i.e. which should be smth a regular dev laptop can handle. At least that would be my prime use case, in combination with some adapted behavior based on malus.
Given that, the boilerplate code should be unified so it lives in one place so we avoid future pain applying changes for the same things in 3 places.
This is slightly in/out-of-scope with this PR, so this is optional for this PR.
There was a problem hiding this comment.
could be added in a future PR, when the need for the functionality arises
companion of paritytech/substrate#9302