---
id: TST-PFM-SEC-219
title: Verification code sender unit checks
kind: unit
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/unit/services/portal/verification-code-sender.spec.ts
implements:
  - ATS-PFM-SEC-020-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: The suite owns its input fixtures and installed doubles.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts#portal
      likely-match: sending a verification code
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts#says
      SMS is off while the origination identity parameter does not exist
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts#says
      SMS is on once the parameter names an origination identity
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts#e-mails
      the code from the invitation sender, in the tenant’s name
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts#texts
      the code from the configured origination identity
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts#refuses
      an SMS while SMS is off, sending nothing
dependency_evidence: >-
  The production decision runs in-process. The suite substitutes message delivery where its
  dependency setup supplies them; those boundaries have no live-service proof here.
evidence:
  - 'services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts'
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: 'services-platform:modules/security/tests/unit/services/portal/verification-code-sender.spec.ts'
  explicit_no_doubles: false
  identified_double_boundaries:
    - message delivery
---
# Verification code sender unit checks

## Verification Boundary

The file evaluates production helpers with controlled inputs in-process. The assertion references identify the source checks for verification code sender.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The production decision runs in-process. The suite substitutes message delivery where its dependency setup supplies them; those boundaries have no live-service proof here.

## Must Not Be Doubled

Keep the production helper, schema, matcher or declaration under examination real. Substituting the decision itself would remove the behavior the assertions exercise.