---
id: TST-PFM-MTD-047
title: endpoints
kind: integration
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#finds
    the tenant’s contacts among the ids asked about, and not one it does not have
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#does
    not find another tenant’s contact, whose row the policy hides
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#finds
    the tenant’s organizations
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#names
    a contact by its registered name field
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#names
    another tenant’s organization in that tenant only, under the policy
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#names
    nothing of an object with no name field, so the API answers the id
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#refuses
    a record that does not exist, naming the field and the object
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#refuses
    an object the registry does not have
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#refuses
    an object the registry has retired
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/endpoints.integration.spec.js#refuses
    an object whose table holds no tenant’s records
fixture_imports:
  - '@rhythmsoftware/macroservice-testing/refusals'
  - '@rhythmsoftware/macroservice-errors/errors'
  - ../../../../services/persistence/endpoints
  - ../../support
test_doubles: []
limitations:
  - Conditional or skipped cases remain outside any claimed passing execution.
unmatched_specification: FND-PFM-MTD-083
binding_assertions: []
---

# Endpoints

## Verification Boundary

This integration suite checks relationship definitions and links within the local test harness. The registered file and pinned revision define its boundary.

## What This Suite Proves

The suite contains executable checks for this module, but no matching detailed scenario is established in this back-fill. The executable coverage finding records that mapping gap. Assertions are evidence of implemented checks; no execution result is claimed.

## What It Does Not Prove

The register does not establish a current passing run or full specification conformance. Conditional or skipped cases remain outside any claimed passing execution.

## Real Dependencies and Test Doubles

The fixture uses PostgreSQL and the imported persistence or API code. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The operation under examination and its asserted stored outcomes must remain real within the declared harness. A fixture cannot replace the write, refusal or transactional effect that the bound scenario checks.