---
id: TST-PFM-ELG-488
title: Eligibility rule summary names checks
kind: unit
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/eligibility/tests/unit/rule-summary-names.spec.js
implements: []
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/eligibility/tests/unit/rule-summary-names.spec.js
    cases:
      - >-
        says the affiliation types of an affiliation in force by name, joined
        with or
      - says one affiliation type by its name
      - keeps the id of an affiliation type whose name could not be read
      - says an affiliation in force of any type without settings
      - says the label of the custom field a condition names
      - says the organization of an is comparison by name
      - >-
        says each organization of a list, keeping the id of one it could not
        read
      - says the contact role of a role condition by name
      - says the ids when no name was read
      - leaves the stored expression and registry as they were
      - names the affiliation types of an added condition
      - names the affiliation types on both sides of a changed condition
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/unit/rule-summary-names.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  No complete capability or feature scenario is mapped to this file; case-level
  ownership remains a coverage finding.
---

# Eligibility rule summary names 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 file contains executable checks, but no complete scenario mapping is established here. Its source test titles identify the remaining mapping work.

## 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.