ashrafee-dev / ashrafee-dev/scamshield-api
Add a Redis fixture or mock for 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
Problem
The test suite currently requires a live Redis instance because rate limiting connects directly to localhost:6379.
Acceptance criteria
- Provide a deterministic fixture or mock for rate-limit behavior.
- Keep tests isolated from a developer’s existing Redis data.
- Document how to run a real Redis-backed check when needed.
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 locating the rate-limiting code and the tests that connect to localhost:6379. Trace how the Redis client is created, then inspect the test setup and project documentation for the appropriate fixture or mock entry point. Done means rate-limit tests are deterministic and isolated, with documented instructions for an optional real Redis check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python, redis
- Domain
- backend, databases, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100