ashrafee-dev / ashrafee-dev/scamshield-api
Add rate-limit behavior tests
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 3
- Forks
- 10
- Avg merge
- 14h 44m
- Merged PRs (30d)
- 9
Description
Goal
Create focused tests for the rate limiter’s important state transitions.
Acceptance criteria
- Cover the first request for an IP.
- Cover requests after the limit is exhausted.
- Cover reset after the configured time window.
- Avoid depending on a developer’s real Redis data.
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
Locate the rate limiter implementation and the existing test setup first, then run the current test suite to understand the project’s conventions. Add focused coverage for the first request, exhausted limits, and time-window reset without using real developer Redis data; done means all listed transitions are tested reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python, redis
- Domain
- api, backend, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100