Add rate-limit behavior tests

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
74/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
fastapi, python, redis
Domain
api, backend, testing-qa

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.

Description

good first issue

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.
Dominant language
Python
Stars
3
Forks
10
Avg merge
14h 44m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ashrafee-dev/scamshield-api

All issues in ashrafee-dev/scamshield-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.