---
id: TST-PFM-ELG-482
title: Eligibility fixtures 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/migration/fixtures.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/migration/fixtures.spec.js
    cases:
      - >-
        holds at least twenty-five fixtures, each with a description, a host,
        criteria and a snapshot
      - answers each fixture’s snapshot exactly
      - >-
        answers no expression with a problem, for any fixture, draft or
        candidate
      - uses every section of the 1.0 schema somewhere
      - raises every ambiguity of 15 §5 somewhere
      - nests advanced rules at least three groups deep somewhere
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/unit/migration/fixtures.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 fixtures 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 exercises its real module dependencies and declares no test doubles. Its source header and imports identify the database, transaction and service boundaries it uses.

## Must Not Be Doubled

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