Skip to content

test: create provider contract tests and versioned response fixture corpus #75

Open
Open
test: create provider contract tests and versioned response fixture corpus#75
Labels
area: gatewaysPayment gateway integrations and provider behaviorarea: testingAutomated test architecture and coverageepicLarge outcome split into multiple deliverable issuespriority: P1High priority; should be addressed nexttestingTest coverage and test suite work
Milestone
Test & Release Quality

Description

@teesofttech
teesofttech
opened on Jul 17, 2026

Why

Fourteen provider-specific test issues exist, but each adapter needs the same behavioral guarantees. A shared contract suite will prevent inconsistent status mapping, amount units, metadata, authentication, refunds, and error handling.

Scope

  • Define reusable create/verify/refund contract tests for IPaymentGateway.
  • Store sanitized success, pending, decline, malformed, rate-limit, and auth-failure fixtures per provider.
  • Test minor-unit/decimal conversion for zero-, two-, and three-decimal currencies.
  • Version fixtures with provider API versions and capture dates.
  • Keep live sandbox tests separate.

Acceptance criteria

  • Every supported provider passes the shared contract or documents an explicit capability exception.
  • Fixtures contain no credentials or customer PII.
  • Parser tests do not use network access.
  • Currency and status mappings are consistent.
  • Existing provider test issues link to and reuse the contract suite.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: gatewaysPayment gateway integrations and provider behaviorarea: testingAutomated test architecture and coverageepicLarge outcome split into multiple deliverable issuespriority: P1High priority; should be addressed nexttestingTest coverage and test suite work

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions