More comprehensive tests for gates
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
We support an operation to "gate" a buffer, where a closed gate means that listeners will not be notified when the buffer gets an update. We have a rudimentary test for this operation, but it would be good to have more comprehensive tests, especially tests that make sure that reachability calculations are working as intended.
Contributor guide
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 the existing rudimentary gate test in the crossflow repository and read the gate operation and reachability calculations it exercises. Add comprehensive coverage for closed and open gates, including reachability behavior, then run the repository's Rust test suite to confirm the cases pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100