---
id: TST-PFM-NOT-025
title: suppressions
kind: api-lifecycle
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/communications/tests/e2e/suppressions.e2e.spec.js
implements:
  - ATS-PFM-NOT-020-02
  - ATS-PFM-NOT-020-03
  - 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-025
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#says
        nothing was recorded the second time, the list being one row per address
  - scenario: ATS-PFM-NOT-020-03
    suite: TST-PFM-NOT-025
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#records
        it as a manual suppression with the note staff gave
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#stores
        the address in its canonical form, lowercase
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#names
        emailAddress in the refusal of an address that is not one
  - scenario: ATS-PFM-NOT-020-04
    suite: TST-PFM-NOT-025
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#refuses
        a release that does not say why as 400
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#leaves
        the suppression active after a release that does not say why
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#records
        who released it and why
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#keeps
        the row for the history, read back when the released are asked for
      - >-
        services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js#answers
        404 for releasing the same suppression twice, there being no active one
        left
evidence:
  - 'services-platform:modules/communications/tests/e2e/suppressions.e2e.spec.js'
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: the dispatcher, the route table, signed-context verification, the
    authorization evaluation, the handlers, the
  - >-
    suppressions persistence service and PostgreSQL with row-level security on.
    Doubled: nothing but the signing key, which is
  - >-
    this run's own. Never doubled: the dispatcher, the route table,
    signed-context verification, the database or the
---

# 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; validate manual suppression input; 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.