---
id: TST-MBR-STR-005
title: Accounting product port against local contract doubles
kind: integration
product_area: membership
module: structure
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-membership
files:
  - modules/structure/tests/integration/services/persistence/accounting-products.integration.spec.ts
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: A uniquely named local workspace and its seeded records; the suite owns its fixture data and cleanup.
evidence:
  - >-
    services-membership:modules/structure/tests/integration/services/persistence/accounting-products.integration.spec.ts
bindings: []
invocation: 'npm run test:integration'
coverage_limit: >-
  Bindings identify the concrete cases executed in this file. A compound specification may also depend on
  other registered suites or remain partly proposed; registration is not a passing execution result.
coverage_gap: FND-MBR-STR-076
provenance: test
source:
  - >-
    services-membership:modules/structure/tests/integration/services/persistence/accounting-products.integration.spec.ts
---

# Accounting product port against local contract doubles

## Verification Boundary

This suite invokes the local implementation against the prepared database and checks its persisted results. Accounting product port against local contract doubles defines the scope of its examples.

## What This Suite Proves

The suite exercises relevant local implementation behavior, but no complete scenario binding is established in this pass. Its presence is registered without counting it as specification proof.

## What It Does Not Prove

Registration supplies no fresh execution result or deployed conformance verdict. Browser behavior, deployed infrastructure and unasserted variants require separate evidence.

## Real Dependencies and Test Doubles

PostgreSQL, local Membership services and the suite’s persistence path are real. The business clock and caller fixtures are controlled by the harness. Accounting tables or product functions are local stand-ins; this suite does not certify the deployed Accounting service.

## Must Not Be Doubled

The Membership path under examination, transaction behavior and database constraints stay real. Replacing those boundaries would remove the persisted proof the suite is intended to supply.