---
id: TST-PFM-ELG-405
title: Attention reminders checks
kind: unit
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/attention/tests/unit/reminders.spec.js
implements:
  - ATS-PFM-ELG-019-03
  - ATS-PFM-ELG-019-04
environment: mock
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 1
isolation: One process with suite-local inputs.
evidence:
  - provenance: test
    source: 'services-platform:modules/attention/tests/unit/reminders.spec.js'
    cases:
      - is none when neither the definition nor the tenant declares one
      - >-
        defaults a declared block to due soon and overdue, daily, three times,
        and escalated when the definition escalates
      - takes the tenant’s override part by part over the declaration
      - is none when the tenant turns it off
      - is none when it reminds of nothing
      - is the due-soon reminder once the item is inside its horizon
      - is nothing while the item is due beyond its horizon
      - is the first overdue reminder once the item is overdue
      - is the overdue repeat of the cadence period the item is in
      - never goes past the policy’s max overdue reminders
      - plans nothing the person already has
      - is the escalated reminder for a person the escalation reaches
      - is no escalated reminder for a person only the first audience reaches
      - is nothing for an advisory definition the person hid
      - still reminds of a required definition whatever the person hid
      - >-
        are one digest row for the next 08:00 in the tenant’s zone, whatever
        fell due
      - are nothing more in a period that already has the item
      - stop after max digests of the item
      - 'wait for Monday 08:00 in a weekly digest'
      - number each day’s period apart from the next
      - 'keep 08:00 across the end of daylight saving time'
      - hold an instant inside a window that crosses midnight
      - 'move a reminder at 23:30 to 07:00 the next morning'
      - move a reminder inside a daytime window to its end the same day
      - schedule a no-digest person’s reminder past their quiet hours
      - hide an advisory or opportunity definition the person named
      - never hide a required definition
      - counts every item in its subject
      - lists each definition once with its items under it
      - 'Finance: Batches awaiting posting'
      - 'Finance: Payouts to reconcile'
      - 'says why each item is in it and when it was due, in the tenant’s zone'
      - links each item to the console
      - escapes what the items’ templates rendered
      - opens the record with the item named for a record destination
      - opens the item list filtered to the definition otherwise
  - provenance: documented
    source: >-
      services-platform:modules/attention/tests/unit/reminders.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  Only the named scenario checkpoints have a verified source binding; execution
  has not been attempted.
---

# Attention reminders checks

## Verification Boundary

This suite checks isolated decisions and validation using the imported inputs. It cannot establish a complete service or browser lifecycle.

## What This Suite Proves

The mapped scenarios identify the capability and feature checkpoints this file exercises. The source test titles preserve the assertion-level evidence.

## What It Does Not Prove

Registration supplies no execution result or conformance decision. Passing isolated checks does not establish deployed dependencies or cross-application delivery.

## Real Dependencies and Test Doubles

The suite runs isolated checks; its imported fixtures and injected collaborators define the substitutions. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

The decision or validator being asserted remains real; returning the expected answer from a substitute defeats the check.