---
id: TST-PFM-NOT-085
title: deliveries
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js
implements:
  - ATS-PFM-NOT-006-03
  - ATS-PFM-NOT-007-04
  - ATS-PFM-NOT-007-07
  - ATS-PFM-NOT-007-09
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Suite-owned records in the prepared integration workspaces; seeded workspace
  identities remain shared fixtures.
assertion_bindings:
  - scenario: ATS-PFM-NOT-006-03
    suite: TST-PFM-NOT-085
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#refuses
        a sent delivery being cancelled: what left is not recalled
  - scenario: ATS-PFM-NOT-007-04
    suite: TST-PFM-NOT-085
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#lets
        only one of two consumers racing for the send win it
  - scenario: ATS-PFM-NOT-007-07
    suite: TST-PFM-NOT-085
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#refuses
        a transition the lifecycle does not allow, changing nothing
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#never
        moves a delivery out of a final status
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#refuses
        a skipped delivery that gives no reason
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#refuses
        rendered content over 8 KB
  - scenario: ATS-PFM-NOT-007-09
    suite: TST-PFM-NOT-085
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#keeps
        the newest fifty events of a delivery and drops the oldest, never
        refusing the report
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js#writes
        a replayed event once: the same provider and provider event id answers
        nothing
evidence:
  - >-
    services-platform:modules/notifications/tests/integration/services/persistence/deliveries.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL, the persistence service, the policy. Doubled: nothing.
    Never doubled: the database, the guard or the service.
---

# deliveries

## Verification Boundary

This suite exercises the local services and prepared PostgreSQL database. API lifecycle cases use signed test contexts through the real route handler; they do not invoke the deployed gateway.

## What This Suite Proves

Its cases exercise stop pending delivery without recalling completed sends; skip final work on redelivery; reject invalid delivery lifecycle writes; deduplicate and bound provider event history.

The registered scenario bindings identify the assertions this executable file contributes. They retain individual test references so that a composite scenario does not become a claim of complete execution by one file.

## What It Does Not Prove

Local outcomes do not prove deployed queues, external provider acceptance, production credentials or complete browser behavior. No fresh execution or conformance result is claimed.

## Real Dependencies and Test Doubles

The notification fixtures use real PostgreSQL and module logic. Queue publication, visibility changes, nudges and installed channel adapters are recorded at their seams when the suite needs them. Signed API contexts replace the authorizer key in API suites.

## Must Not Be Doubled

Database constraints, workspace policy, state guards and the service operation under test must remain real. Recording a provider or queue call must not replace the submission, claim or outcome logic being checked.