Joystream / Joystream/joystream
Runtime testing & benchmarking refactoring
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
WIP:
The further ideas to improve testing and benchmarking experience would be introducing separate crates for tests and benchmarks with the common code.
Requires substantial planning about how to do this across all pallets.
┆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 inventorying how runtime tests and benchmarks are organized across the pallets, then identify the common code that could be shared. The issue names no files or tests, so the initial deliverable is a cross-pallet design and implementation plan for separate test and benchmark crates, followed by maintainers’ agreement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100