---
id: TST-PFM-NOT-039
title: template copies
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/dispatch/template-copies.integration.spec.js
implements:
  - ATS-PFM-NOT-016-03
  - ATS-PFM-NOT-017-10
  - ATS-PFM-NOT-019-08
  - ATS-PFM-NOT-020-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: >-
  Suite-owned records in the prepared integration workspaces; seeded workspace
  identities remain shared fixtures.
assertion_bindings:
  - scenario: ATS-PFM-NOT-016-03
    suite: TST-PFM-NOT-039
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#refuses
        more than ten copies
  - scenario: ATS-PFM-NOT-017-10
    suite: TST-PFM-NOT-039
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#still
        sends to the contact
  - scenario: ATS-PFM-NOT-019-08
    suite: TST-PFM-NOT-039
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#suppresses
        the copy that bounced
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#does
        not suppress the contact
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#records
        the copy's bounce on the message history without marking the contact's
        message bounced
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#marks
        the message delivered when the contact's own delivery arrives
  - scenario: ATS-PFM-NOT-020-06
    suite: TST-PFM-NOT-039
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js#sends
        the deliverable BCC copy and drops the one this environment may not
        e-mail
evidence:
  - >-
    services-platform:modules/communications/tests/integration/services/dispatch/template-copies.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL, the template, submission, acceptance, dispatcher, send and
    feedback services. Doubled: SES at the
  - >-
    transport, the object store, the dispatcher's nudge and the send queue.
    Never doubled: the database or the services.
---

# template copies

## 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 validate template fields while retaining unfinished drafts; allow display configuration without caller-selected addresses; keep copy feedback separate from primary delivery; apply the configured nonproduction policy.

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.