---
id: TST-PFM-NOT-065
title: render preview
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/templates/render-preview.integration.spec.js
implements:
  - ATS-PFM-NOT-016-06
  - ATS-PFM-NOT-016-11
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-06
    suite: TST-PFM-NOT-065
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#is
        told it is Handlebars, with the line and column of the tag
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#is
        one problem naming what was found and where
  - scenario: ATS-PFM-NOT-016-11
    suite: TST-PFM-NOT-065
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#renders
        the same subject, character for character
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#renders
        the same HTML body, character for character
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#is
        an answer and not a refusal: the content is the author’s to fix
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#names
        that empty custom field, and only it, in emptyFields
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#leaves
        every communications table with exactly the rows the notice left
      - >-
        services-platform:modules/communications/tests/integration/services/templates/render-preview.integration.spec.js#puts
        nothing on the send queue
evidence:
  - >-
    services-platform:modules/communications/tests/integration/services/templates/render-preview.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),
    CRM's registration, the metadata
  - >-
    acceptance and the preview itself. Doubled: the communication object store,
    the send queue (recorded) and the dispatcher's
  - >-
    nudge (recorded). Never doubled: the database, the registry, the renderer,
    acceptance or the preview under test.
---

# render preview

## 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 report unsafe and invalid content locations; preview through the delivery renderer without sending.

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.
