---
id: TST-PFM-MTD-043
title: associations events
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.events.integration.spec.js
implements:
  - ATS-PFM-MTD-015-01
  - ATS-PFM-MTD-015-03
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.events.integration.spec.js
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#writes
    exactly one ledger row, objects.association.created
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#carries
    the declared payload: the identifiers, primary and the dates
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#names
    the association as its subject and its type as its scope
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#writes
    one queue row naming the event
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
    objects.association.ended for an end, with its end date
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
    objects.association.ended for an update that gives an open association an end date
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
    nothing for an update of its other fields
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
    objects.association.ended when a delete ends a dated type’s open association instead
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
    objects.association.deleted for a delete, with the association as it was
  - >-
    services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
    nothing for a refused end, and leaves the create’s event alone
fixture_imports:
  - '@rhythmsoftware/macroservice-testing/refusals'
  - '@rhythmsoftware/macroservice-testing/stage'
  - '@rhythmsoftware/macroservice-errors/errors'
  - ../../../../services/persistence/associations
  - ../../support
  - ../../../../../custom-objects/tests/integration/business-events
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-015-01
    provenance: test
    source:
      - >-
        services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
        objects.association.deleted for a delete, with the association as it was
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
  - scenario: ATS-PFM-MTD-015-03
    provenance: test
    source:
      - >-
        services-platform:modules/associations/tests/integration/services/persistence/associations.events.integration.spec.js#publishes
        nothing for an update of its other fields
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Associations events

## 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 bindings identify the detailed or feature scenarios whose outcomes have assertions in this suite. Original case references remain attached to the detailed scenarios so a reviewer can inspect the exact assertion. 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.