test: add comprehensive tests for rate limiting and anti-spam

[greatest0fallt1me]

Description:

Write comprehensive test cases for rate limiting enforcement.

Requirements and Context:

• Must achieve minimum 95% test coverage
• Should test enforcement at and over limit
• Should test window expiry (limit resets)
• Should test per-user and per-event limits
• Should test admin limits for event creation
• Should test error messages and events

Suggested Execution:

1. Fork the repo and create a branch

   git checkout -b test/rate-limiting-tests

2. Implement changes

   • Write tests: src/test.rs (rate limiting tests)
   • Validate test coverage

3. Test and commit

   • Run tests with coverage; include test output

Example Commit Message:

test: add comprehensive tests for rate limiting and anti-spam

Guidelines:

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 48 hours

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Georgechisom]

@Georgechisom has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I love to work on this issue and deliver an excellent result, please help assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Georgechisom to this issue.

[Sobilo34]

@Sobilo34 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi! Sobil is here

As a Web3 software engineer with experince in building full start blockchain products, both smart contract and frontend integration. I will do this project if it is assigned to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sobilo34 to this issue.

[MerlinTheWhiz]

@MerlinTheWhiz has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Let me work on this one

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MerlinTheWhiz to this issue.

[dannyy2000]

@dannyy2000 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi maintainer, can i work on this? ETA 4 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dannyy2000 to this issue.

[augustine00z]

@augustine00z has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I’d like to be assigned to this issue.
I can write comprehensive rate-limiting tests covering limits, window expiry, per-user/per-event rules, admin restrictions, and error cases, with ≥95% coverage.

ETA: 36–48 hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @augustine00z to this issue.

[victorisiguzoruzoma874]

@victorisiguzoruzoma874 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello maintainer, I would love to work on this for you ETA 2hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @victorisiguzoruzoma874 to this issue.

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

This looks straightforward and I’d love to work on it I’ll add a comprehensive rate-limiting/anti-spam test suite in src/test.rs that validates (1) enforcement exactly at the limit and over the limit, (2) window expiry behavior where limits reset after the configured interval, (3) per-user limits (one user hitting a cap doesn’t affect others) and per-event limits (caps tracked independently per event), (4) admin-specific limits for event creation (including rejection once exceeded), and (5) correctness of error variants/messages plus any events emitted during rate-limit hits (count + expected payload/fields). I’ll keep the tests deterministic (mocked time/ledger ticks if the contract uses timestamps/ledgers), run the suite with coverage to meet the 95% minimum, and include the coverage + test output in the PR under branch test/rate-limiting-tests with commit message test: add comprehensive tests for rate limiting and anti-spam.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Obiajulu-gif to this issue.