OpenZeppelin / OpenZeppelin/Event-Scanner
test: Add Robustness Tests
Open
Nobody has claimed this yet.
priority: medium
type: test
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
Some of the necessary test cases:
- Slow RPC response #135
- Failed RPC response #135
- Slow event processing, causing channel to be filled
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 RPC and event-processing tests, then review the cases referenced by issue #135. Add coverage for slow RPC responses, failed RPC responses, and slow event processing that fills the channel; done means these robustness scenarios are exercised by the test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100