Joystream / Joystream/joystream
Runtime update integration test
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
During runtime upgrade proposals PR review https://github.com/Joystream/joystream/pull/3339 , I've noticed that there is a flow updateRuntime.ts in integration tests that doesn't seem to be called from any scenario, thus not used.
Investigate why it's not used (anymore?), either call it in one of the existing scenarios, create a new scenario or delete it if it's not useful anymore. Plus, consider adding a test for https://github.com/Joystream/joystream/pull/3339/files behavior and assess other on-runtime-update logic that could be tested as well.
┆Issue is synchronized with this Asana task by Unito
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating updateRuntime.ts in the integration tests and checking which existing scenarios invoke it, then review the behavior changed by PR 3339. Done means deciding whether the flow should be used, replaced with a new scenario, or deleted, with appropriate runtime-update behavior covered by integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- blockchain, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100