Write tests for ContractEventFeed initial load polling live toggle and error states

[k-deejah]

Problem

src/components/ContractEventFeed.tsx fetches events on mount, supports live polling via setInterval, handles error and empty states, and exposes a Live/Paused toggle. None of this is tested.

The stale closure polling bug (load not in dependency array — tracked separately) makes this component especially risky to modify without tests — there is no safety net to verify correct polling behavior after a fix. Three specific untested behaviors: (1) the initial fetch fires on mount with the correct contractId; (2) the Live/Paused toggle stops and restarts the polling interval; (3) when contractId changes, the component fetches for the new ID, not the old one.

Solution

Write React Testing Library tests using vi.useFakeTimers() for polling control. Test:

• Initial fetch is called on mount with the correct contractId prop
• Events render in a list after a successful fetch
• Empty state renders when fetch returns an empty array
• Error message renders when fetch returns an error
• Polling calls getEvents at the configured pollInterval using fake timers
• Toggling the Live button pauses polling (no further calls after toggle)
• Changing contractId prop triggers a new fetch for the new ID

Acceptance Criteria

• Initial fetch fires with the correct contractId
• Event list renders returned events
• Empty state renders when no events exist
• Error state renders error message
• Polling fires at correct interval with fake timers
• Live toggle stops polling when switched to Paused
• Changing contractId fetches for the new contract
• All tests pass with npm test

---

Note for Contributors: If you're assigned to this issue, write a clear and detailed description for your pull request. Explain what was changed, why it was needed, how it was implemented, and include any relevant testing or screenshots where applicable.

[Nathanpvd]

@Nathanpvd has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I’d be happy to take responsibility for this issue and work toward submitting a well-tested, quality pull request.

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

[Favouratambi]

@Favouratambi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd love to work on this issue. I'll keep the implementation simple, clean, and well-tested.

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

[tzar-deek]

@tzar-deek has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer can I get on this issue for you real quick, as I am active right now on the wave I also hopes this open doors to us working on this project some more after the wave, will love to help in the course of this journey.

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

[drips-wave]

Congratulations, @tzar-deek! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @tzar-deek: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊