---
id: TST-PFM-NOT-021
title: notifications
kind: unit
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - components/notifications/__tests__/notifications.test.tsx
implements:
  - ATS-PFM-NOT-009-05
  - ATS-PFM-NOT-009-07
  - ATS-PFM-NOT-009-08
  - ATS-PFM-NOT-010-05
  - ATS-PFM-NOT-011-03
  - ATS-PFM-NOT-011-04
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-009-05
    suite: TST-PFM-NOT-021
    assertions:
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#marks
        a row read from its menu: the route is called and the unread count drops
        by one
  - scenario: ATS-PFM-NOT-009-07
    suite: TST-PFM-NOT-021
    assertions:
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#Send
        Me a Test asks for a test, which arrives in the inbox
  - scenario: ATS-PFM-NOT-009-08
    suite: TST-PFM-NOT-021
    assertions:
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#marks
        a row read from its menu: the route is called and the unread count drops
        by one
  - scenario: ATS-PFM-NOT-010-05
    suite: TST-PFM-NOT-021
    assertions:
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#tells
        why in a sentence in the Why sheet
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#words
        the milestone from the delivery summary while the resolution is not
        there yet
  - scenario: ATS-PFM-NOT-011-03
    suite: TST-PFM-NOT-021
    assertions:
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#lists
        the requests that told nobody in the Requests view, with the first
        problem, and opens the chain on one
  - scenario: ATS-PFM-NOT-011-04
    suite: TST-PFM-NOT-021
    assertions:
      - >-
        react-console:components/notifications/__tests__/notifications.test.tsx#opens
        the chain on a request whose problems are null or absent (DEF-NT-0011)
evidence:
  - 'react-console:components/notifications/__tests__/notifications.test.tsx'
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    The three notification screens against the MSW double
    (`mocks/handlers/notifications.ts`), through the real client and
---

# notifications

## 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 update personal read and archive state; send a personal pipeline test; open an assignment item and update its count; display the explanation without raw reason tokens; include requests that produced no notices; read complete request, notice and delivery links.

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.