---
id: TST-PFM-NOT-097
title: template overrides
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/template-overrides.integration.spec.js
implements:
  - ATS-PFM-NOT-015-05
  - ATS-PFM-NOT-015-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-015-05
    suite: TST-PFM-NOT-097
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#starts
        a draft at version 1 for the definition, channel and locale
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#supersedes
        the previous active version when another is published
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#leaves
        exactly one active version per definition, channel and locale
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#refuses
        to publish wording that names a field the definition does not declare
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#refuses
        to publish an in-app title that renders over 140 characters
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#takes
        the active version out of use so the product’s wording applies again,
        and audits it
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#publishes
        an e-mail override that changes only the subject, the HTML and text
        inheriting from the product
  - scenario: ATS-PFM-NOT-015-06
    suite: TST-PFM-NOT-097
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js#publishes
        a draft: active, stamped with the time and the person, and audited
evidence:
  - >-
    services-platform:modules/notifications/tests/integration/services/persistence/template-overrides.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL, the persistence service, the renderer, the security audit
    trail, the policy. Doubled: nothing. Never
---

# template overrides

## 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 stored wording overrides without runtime effect; audit successful workspace configuration writes.

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.