Add RTL tests for MilestonesList rendering across all four statuses

[mikewheeleer]

Description

src/components/__tests__/MilestonesList.test.tsx should comprehensively cover how MilestonesList.tsx renders Pending, Completed, Paid, and Disputed milestones, including payout formatting via the preferences provider. Add cases for the empty list, missing due dates, and the total count. This locks in the core milestone display behavior.

Requirements and context

• Scoped to TalentTrust Talenttrust-Frontend (Next.js App Router + TS + Tailwind). Align with milestone/contract/reputation flows and the backend API.
• Wrap the component with the preferences provider to assert formatAmount output.
• Assert each status renders its badge and the count matches input length.
• Must be accessible (WCAG 2.1 AA), responsive, tested, and documented. Concrete acceptance criteria: 95%+ coverage of the component logic.

Suggested execution

• Fork the repo and create a branch:
  • git checkout -b test/milestones-list-coverage
• Implement changes:
  • src/components/MilestonesList.tsx (real or new)
  • Tests: src/components/__tests__/MilestonesList.test.tsx (Jest + React Testing Library)
  • Docs: docs/components/MilestonesList.md
  • Ensure keyboard nav, focus states, ARIA, color-contrast, and responsive breakpoints

Test and commit

• Run: npm test, npm run lint, npm run build
• Cover edge cases (loading, empty, error, no-wallet, slow network, small screens)
• Include screenshots/notes and a11y check results in the PR

Example commit message

test(ui): cover milestone statuses and formatting

Guidelines

• Accessible (WCAG 2.1 AA), responsive, keyboard-navigable
• Minimum 95% coverage on new/changed component logic
• Clear documentation
• Timeframe: 96 hours from assignment

[ObaHacker]

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

Good Morning Ser, How are you doing?
I’ve looked into the issue, and I have a clear path to a clean fix.

I’ll implement it in a way that matches the current architecture and avoids introducing extra complexity.

Thank you for your consideration.

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

[drips-wave]

Congratulations, @ObaHacker! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @ObaHacker: 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 🌊