clockworklabs / clockworklabs/SpacetimeDB
Test coverage - Smoketest with multiple parallel subscribers
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
It would be good to have a smoketest of some kind that creates multiple parallel subscribers. For now, even a "they all receive the values and don't deadlock" test is an improvement.
Definition of "Done"
WIP, pls help
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
The issue names no files, tests, or entry points. Start by locating the existing smoketest or subscriber-test harness, then determine how to create multiple parallel subscribers. Done means a test shows that all subscribers receive the values without deadlocking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100