---
id: TST-PFM-NOT-115
title: slack system render
kind: unit
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/notifications/tests/unit/slack-system-render.spec.js
implements:
  - ATS-PFM-NOT-013-05
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Per-process test inputs and installed doubles.
assertion_bindings:
  - scenario: ATS-PFM-NOT-013-05
    suite: TST-PFM-NOT-115
    assertions:
      - >-
        services-platform:modules/notifications/tests/unit/slack-system-render.spec.js#is
        exactly a bold title and the body, the Rhythm HQ context line in Eastern
        time, one URL button and a plain fallback
      - >-
        services-platform:modules/notifications/tests/unit/slack-system-render.spec.js#reads
        the instant in Eastern time on the other side of daylight saving time
      - >-
        services-platform:modules/notifications/tests/unit/slack-system-render.spec.js#cuts
        the section text at 3,000 characters
      - >-
        services-platform:modules/notifications/tests/unit/slack-system-render.spec.js#escapes
        the three characters Slack treats as control characters, and nothing
        else
      - >-
        services-platform:modules/notifications/tests/unit/slack-system-render.spec.js#names
        the channel by key and carries no id, so what is stored on a delivery
        names no workspace identifier
evidence:
  - >-
    services-platform:modules/notifications/tests/unit/slack-system-render.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: the renderer and Moment Timezone. Doubled: nothing. Never doubled: the
    renderer.
---

# slack system render

## Verification Boundary

This suite checks isolated calculations, validation or presentation with process-local inputs. It does not establish a deployed workflow.

## What This Suite Proves

Its cases exercise render stable, bounded Slack content.

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 test file identifies its pure inputs or presentation doubles. Console component suites use recorded request handlers; pure validation suites require no external provider.

## Must Not Be Doubled

The calculation, validator or component under test must execute its real implementation. Doubles supply inputs and external responses without replacing the behavior being proved.