Repository navigation
[Testing] Zero test coverage for HomeScreen — activity feed rendering, streak display, pending proof sync, and EarningsSummary integration #148
Description
Why this matters now
HomeScreen is the first screen users land on after authentication and the primary engagement loop surface (streak, recent activity, earnings). It integrates five stores (userStore, activityStore, walletStore), useProofSubmit (for offline sync), and EarningsSummary. It has no test file. Any regression in how activities render, how the streak is displayed, or how the PendingProofsBanner triggers sync is invisible.
Problem / What
src/screens/HomeScreen.tsx (250 lines) has no test file. The screen:
- Reads
activities,streak,bestStreakfromactivityStore - Calls
recomputeStreaks()on mount - Renders
EarningsSummary(which has its own useMemo gaps, per issue [Performance]EarningsSummarytriple O(n) computation on every render with no memoization #57) - Renders
PendingProofsBannerwithpendingCount/isSyncingfromuseProofSubmit - Shows the last 5 activities with status-based styling
Key Challenges
useProofSubmitcallsloadQueue()synchronously in its initializer — the mock must stubproofQueue.loadQueueto return a controlled array.recomputeStreaksmust be called on mount; test withjest.fn()to verify the call.- Activity status styling (confirmed=green, pending=yellow, failed=red) is a critical correctness concern — snapshot or explicit style assertion is needed.
Acceptance Criteria
-
HomeScreen.test.tsxcreated with tests for: greeting text rendering, profile name fromuserStore, streak value fromactivityStore, last-5-activities rendering with correct status labels,PendingProofsBannershown whenpendingCount > 0,recomputeStreakscalled on mount, "Browse Tasks" button navigates toTaskstab. - All tests pass in CI.
Relevant files / functions
src/screens/HomeScreen.tsxsrc/store/activityStore.tssrc/store/userStore.tssrc/hooks/useProofSubmit.ts— mocksrc/services/proofQueue.ts— mockloadQueue
Out of scope
EarningsSummaryinternal rendering (tested separately incomponents.test.tsx).- The sync retry flow (tested in
useProofSubmit.test.tsx).
Activity
devprom6 commentedon Aug 28, 2026
I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.
I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.
My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.
grantfox-oss commentedon Aug 28, 2026
🦊 GrantFox — @devprom6 has been assigned to this issue as part of the Third Campaign campaign!
Next steps:
Closes #148)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Aug 28, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!
@devprom6's PR #153 was approved and merged by @cybermax4200.
🏆 @devprom6: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (592 total points). Track your full progress on GrantFox.
👏 Great work, @devprom6! Keep contributing to ecotask-network.