Establish test infrastructure with Freighter/RPC mocking and cover highest-risk hooks

[meshackyaro]

Description

No *.test.*/*.spec.* file exists anywhere in this repo, no test framework is installed, and .github/workflows/ci.yml only runs lint, typecheck, and build. The highest-risk logic in the codebase — wallet connection/polling (hooks/useAccount.ts), the on-chain event placeholder (hooks/useSubscription.ts), and the API routes that silently fall back to mock data (pages/api/profile.ts, pages/api/usdc-price.ts) — has zero coverage. This is what makes it hard: none of it can be tested without properly mocking the Freighter browser extension API and Soroban RPC responses, which the codebase has no existing pattern for.

Component

Frontend

Difficulty

🔴 Hard

Tasks

• Choose and install a test framework compatible with Next.js 13 Pages Router (Jest + React Testing Library is the conventional choice)
• Build a reusable mock for @stellar/freighter-api (connect/disconnect/getAddress/signTransaction) so wallet-dependent hooks/components are testable without a real extension
• Build a reusable mock/fixture layer for Soroban RPC responses (simulate results, ledger entries) for when the contract-integration work lands
• Write coverage for useAccount.ts (connect, disconnect, switch-account, polling behavior) and the API routes' mock-fallback branches
• Wire test/test:coverage scripts into package.json and add a test step to .github/workflows/ci.yml

Acceptance Criteria

• A test framework is installed and runnable via npm test
• Freighter and RPC mocking utilities exist and are documented (README or a testing.md) so future contract-integration work can reuse them
• useAccount.ts and both API routes have meaningful test coverage (not just snapshot/smoke tests)
• CI runs the test suite on every PR and fails the build on test failures

Estimated Time

2-3 days

[Opulencechuks]

I am confident that I can implement this issue having worked on something similar in the past

[onyekachi66]

I would like to work on this issue I am sure I can solve it. my eta is 4 hrs

[Anichris-koded]

Hi my name is Koded, and I’m a professional software engineer experienced in building robust testing infrastructure for blockchain applications. I can establish reliable Freighter and RPC mocking, enabling deterministic tests for wallet interactions, transaction flows, and network-dependent behavior while covering the highest-risk hooks. My approach focuses on realistic mocks, critical edge cases, strong regression coverage, and improved confidence in production-ready blockchain integrations.

[Visionaryjoe]

worked on frontend designs, i will glady take part in building this test infrastructure

[ABEEGOLD]

Hello Maintainer,

I've reviewed the issue and have experience with Next.js, React hooks, TypeScript, API testing, and CI workflows. I can set up a maintainable testing infrastructure using Jest and React Testing Library, create reusable mocks for the Freighter API and Soroban RPC responses, and add meaningful coverage for wallet connection flows, polling behavior, and API fallback logic. I'll also integrate test execution into the existing CI pipeline and document the testing approach so future contributors can easily extend it.

[grantfox-oss]

🦊 GrantFox — @ABEEGOLD has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #82)
2. Your PR will be reviewed by the trustflow-protocol maintainers

Good luck! Track your progress on GrantFox.