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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
(Rephrasing @kianenigma) An integration test to make sure the payload that is built in various try-runtime-cli commands matches the trait def (expected payload). We could: move trait TryRuntime to sp-try-runtime (or keep it where it is). Provide a fake implementation of it, and call into that fake implementation with the payload. Or, a realistic test that actually builds a wasm from substrate-node-template, but I don't know how to do that exactly.
Solution
No response
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered:
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Motivation
try-runtime
has generally low test coverage.follow-chain
recently broke for a while without anyone noticing, and there're a few unresolvedtry-runtime
related issues.Request
(Rephrasing @kianenigma) An integration test to make sure the payload that is built in various try-runtime-cli commands matches the trait def (expected payload). We could: move
trait TryRuntime
tosp-try-runtime
(or keep it where it is). Provide a fake implementation of it, and call into that fake implementation with the payload. Or, a realistic test that actually builds a wasm from substrate-node-template, but I don't know how to do that exactly.Solution
No response
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: