---
id: TST-PFM-ELG-401
title: Attention reminders checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/attention/tests/integration/services/reminders/reminders.integration.spec.js
implements:
  - ATS-PFM-ELG-019-04
  - ATS-PFM-ELG-019-05
  - ATS-PFM-ELG-019-06
environment: local
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 5
isolation: Prepared local test database with suite-owned fixture keys and cleanup.
evidence:
  - provenance: test
    source: >-
      services-platform:modules/attention/tests/integration/services/reminders/reminders.integration.spec.js
    cases:
      - createJobExecutionContext
      - >-
        plans one reminder per person an item reaches: a user audience, and a
        responsibility’s holder
      - plans nothing for a person who snoozed the item
      - plans nothing of an advisory definition the person hid
      - plans nothing for an item due beyond its horizon
      - plans nothing more on a second sweep
      - 'sends one message per person, the admin’s listing both of their items'
      - >-
        asks communications for the caller-rendered reminder purpose, to the
        user’s address, with console links
      - >-
        asks for a request communications’ own acceptance finds nothing wrong
        with
      - stamps every reminder it carried with the request that carried it
      - sends nothing on a second run
      - >-
        plans a daily-digest person’s reminder as a digest for the next 08:00,
        and does not send it before then
      - skips a due reminder whose item was resolved before it went
      - moves a due reminder inside the person’s quiet hours to their end
  - provenance: documented
    source: >-
      services-platform:modules/attention/tests/integration/services/reminders/reminders.integration.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 the module through real local service and database code at the entry points used by its test cases.

## 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. Checks beyond the file’s reachable assertions remain unverified, including production configuration.

## Real Dependencies and Test Doubles

The suite uses local integration fixtures. Signing, caches, provider responses or outbound delivery may be supplied by fixtures where the source declares a substitution. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

The module behavior under assertion, transaction boundary and database constraint being checked remain real. Fixture setup cannot stand in for the asserted write or refusal.