Skip to content

test(frontend): add contract-driven tests for transfer, quote, and error states #282

Description

@arisu6804

Problem

Schema or precision changes can silently break the send flow or misrepresent transfer outcomes.

Objective

Deliver a production-quality improvement to API adapters, send flow, and receipt screens that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

  • Maintain versioned fixtures for quotes, validation, authorization, pending, settled, failed, and expired states; assert safe numeric parsing.

Acceptance criteria

  • Breaking response changes fail with actionable diffs; all supported states render correctly; tests are deterministic without live providers.

Required validation

  • Contract fixture, component, error-state, precision, and deterministic integration tests.
  • Existing tests and CI remain passing.
  • Add regression coverage for the original failure mode.
  • Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

  • Keep the PR focused and explain design tradeoffs, compatibility impact, and test evidence.
  • Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

  • Broad rewrites not required by the acceptance criteria.
  • Changes to unrelated services, contracts, or user flows.

Metadata

Metadata

Assignees

Labels

GRANTFOX OSSOpen-source issue tracked by GrantFoxMAYBE REWARDEDThis issue may carry a rewardThird CampaignThird Campaign contributionenhancementNew feature or requestpriority:mediumMedium implementation priority

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions