---
id: TST-PFM-MTD-046
title: associations queries
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/associations.queries.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/associations.queries.integration.spec.js
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#answers
    the association as stored, every column but the two keys mapped and the empty ones absent
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#answers
    undefined for an id the tenant does not have
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#answers
    undefined for another tenant’s association, which the policy hides
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#lists
    a record’s open associations in both directions, in id order, each read from the record’s side
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#answers
    each listed association whole beside what the list adds, as a literal record
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#lists
    the record from the to side of a type, with the reverse label
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#adds
    the ended associations when asked, with their end dates
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#narrows
    the list to one type
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#pages
    by id: a page of the limit with a cursor, then the rest with none
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#does
    not list a record of the same id under another object
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#lists
    nothing of this tenant to another tenant asking about the same record id
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#refuses
    an objects.* record while no resolver answers for the objects application
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.queries.integration.spec.js#refuses
    a cursor this list did not answer
fixture_imports:
  - ../../../../services/persistence/endpoints
  - '@rhythmsoftware/macroservice-testing/refusals'
  - '@rhythmsoftware/macroservice-testing/stage'
  - '@rhythmsoftware/macroservice-errors/errors'
  - ../../../../services/persistence/associations
  - ../../support
test_doubles: []
limitations: []
unmatched_specification: FND-PFM-MTD-083
binding_assertions: []
---

# Associations queries

## 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. Behavior outside the suite’s fixtures and assertions remains unverified.

## 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.