---
id: TST-PFM-NOT-023
title: messages
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/messages.e2e.spec.js
implements:
  - ATS-PFM-NOT-018-07
  - ATS-PFM-NOT-019-04
  - ATS-PFM-NOT-019-05
  - ATS-PFM-NOT-019-07
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-018-07
    suite: TST-PFM-NOT-023
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#answers
        200 and the message cancelled
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#refuses
        cancelling the same message twice as 400, it no longer being queued
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#refuses
        cancelling a message that was withheld rather than drafted as 400
  - scenario: ATS-PFM-NOT-019-04
    suite: TST-PFM-NOT-023
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#lists
        only the messages of the request asked about
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#lists
        only the messages about the source record asked about
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#answers
        the rest of the list after that cursor, repeating nothing
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#refuses
        a cursor this list never answered as 400
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#refuses
        a source type given without its id as 400
  - scenario: ATS-PFM-NOT-019-05
    suite: TST-PFM-NOT-023
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#answers
        the HTML and text bodies rendered for this recipient
  - scenario: ATS-PFM-NOT-019-07
    suite: TST-PFM-NOT-023
    assertions:
      - >-
        services-platform:modules/communications/tests/e2e/messages.e2e.spec.js#lists
        nothing of this tenant under the other tenant
evidence:
  - 'services-platform:modules/communications/tests/e2e/messages.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, real
  - >-
    acceptance, the messages 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
---

# messages

## 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 allow cancellation only before submission; filter and page communication history; require sensitive permission for available body content; enforce workspace isolation on all mail detail.

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.