---
id: TST-PFM-NOT-050
title: suppressions
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/communications/tests/integration/services/persistence/suppressions.integration.spec.js
implements:
  - ATS-PFM-NOT-020-02
  - ATS-PFM-NOT-020-04
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-020-02
    suite: TST-PFM-NOT-050
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/suppressions.integration.spec.js#canonicalizes
        the address, so the same mailbox written two ways is one suppression
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/suppressions.integration.spec.js#records
        nothing for an address already suppressed, so a repeated bounce adds no
        second row
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/suppressions.integration.spec.js#keeps
        the reason of the suppression already in force when it is suppressed
        again
  - scenario: ATS-PFM-NOT-020-04
    suite: TST-PFM-NOT-050
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/suppressions.integration.spec.js#lets
        the address be suppressed again afterwards
evidence:
  - >-
    services-platform:modules/communications/tests/integration/services/persistence/suppressions.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL (the prepared integration database, row-level security on)
    and the suppressions persistence service.
  - >-
    Doubled: nothing. Never doubled: the database, its constraints, or the
    operations under test — the ten tied rows are
---

# suppressions

## 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 deduplicate canonical address suppression; record deliberate suppression release.

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 communication fixtures use real PostgreSQL and module logic. Shared support records queue and transport calls and stores objects in memory; sender provisioning substitutes a provider identity store. 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.