---
id: TST-PFM-INT-566
title: subscriptions
kind: integration
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js
implements:
  - ATS-PFM-INT-014-01
  - ATS-PFM-INT-014-02
  - ATS-PFM-INT-014-03
  - ATS-PFM-INT-014-04
  - ATS-PFM-INT-014-05
  - ATS-PFM-INT-014-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - >-
    services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#refuses
      a subscription to a type the manifest does not subscribe, naming the field
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#refuses
      a subscription to a type the installation has not accepted, naming the type, and writes nothing
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#fails
      a delivery of a type the installation withdrew after the subscription was made, without calling the
      adapter
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#refuses
      a filter the shared conditions grammar refuses, naming the field
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#refuses
      a second subscription of the same installation, connection and type
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#turns
      a CRM change event into a queued delivery of the catalog projection, never the row
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#writes
      one delivery for a change event delivered twice
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#records
      a delivery its filter refused as skipped_filter, and queues nothing for it
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#writes
      nothing for a change event of a tenant that no longer exists, and answers it succeeded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#refuses
      a batch that is not the contract at all
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#delivers
      through the adapter’s EVENTS entry with the delivery, its attempt and a lease, and records the
      acknowledgement
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#retries
      a classified failure with the async backoff and records the delivery dead after six attempts
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#retries
      a dead delivery an operator asks for, from its first attempt
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#pauses
      a subscription after fifty dead deliveries in a row and tells its administrators once
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js#delivers
      nothing more to a paused subscription, and resumes it with its count reset
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/subscriptions/subscriptions.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# subscriptions

## Verification Boundary

This database and service suite exercises subscriptions. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.