Repository navigation
[Testing] Zero test coverage for TaskListScreen — filter, sort, status, radius, search, and infinite-scroll interactions #146
Description
Why this matters now
TaskListScreen is the primary discovery surface. It has seven independently controllable UI dimensions (type filter, status filter, search query, sort mode, radius, scroll to load more, pull-to-refresh) and uses useTaskFeed + sortTasks + filterTasksByQuery + filterTasksByStatus together. Any regression in how these interact is invisible in CI. The useTaskFeed.test.ts tests cover the hook in isolation but not the composed screen behavior.
Problem / What
src/screens/TaskListScreen.tsx (313 lines, 7 filter controls) has no test file. The screen drives useTaskFeed with type, lat/lng/radius, sort params, then client-side-filters the result with query and statusFilter. Bugs at the composition seam (e.g., a type filter + status filter combined, or a sort + search combined) are not caught by any existing test.
Key Challenges
useTaskFeedmust be mocked to return controlled task lists;useStellarWalletanduseLocationalso need mocks.- The FlatList
onEndReached(loadMore) andonRefreshpaths are notoriously tricky to trigger inreact-test-renderer; usefireEvent.scrollwith the correctcontentOffset. - Radius buttons are rendered inside a nested
ScrollView— interaction requiresfireEventon the inner view's testIDs.
Acceptance Criteria
-
TaskListScreen.test.tsxcreated with tests for: type filter changes theuseTaskFeedparams, status filter client-side-filters the list, search query filters by title, sort mode changes are reflected, radius button changes trigger a feed refresh,loadMorefires when the list reachesonEndReachedThreshold, pull-to-refresh callsrefresh. - At least one combined test: type filter + search query together produce the correct visible task list.
- All tests pass in CI.
Relevant files / functions
src/screens/TaskListScreen.tsxsrc/hooks/useTaskFeed.ts— mocksrc/utils/sortTasks.ts—filterTasksByQuery,filterTasksByStatus,sortTasks
Out of scope
- Testing
TaskCardrendering (covered incomponents.test.tsx). - End-to-end location permission flows.
Activity
devOgazi 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 — @devOgazi has been assigned to this issue as part of the Third Campaign campaign!
Next steps:
Closes #146)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Aug 29, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!
@devOgazi's PR #155 was approved and merged by @cybermax4200.
🏆 @devOgazi: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (694 total points). Track your full progress on GrantFox.
👏 Great work, @devOgazi! Keep contributing to ecotask-network.