---
id: TST-PFM-ELG-410
title: Eligibility definition key alias checks
kind: api-lifecycle
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/eligibility/tests/e2e/eligibility-definition-key-alias.e2e.spec.js
implements:
  - ATS-PFM-ELG-001-01
  - ATS-PFM-ELG-001-15
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/eligibility/tests/e2e/eligibility-definition-key-alias.e2e.spec.js
    cases:
      - 'creates a definition from id, answering id and key equal'
      - 'creates a definition from key, answering id and key equal'
      - accepts id and key when they are equal
      - 'refuses id and key that differ, 400, naming both'
      - creates nothing when id and key differ
      - 'refuses a create naming neither id nor key, 400'
      - 'refuses a key outside the configuration-id grammar, 400'
      - answers the definition of a get with key equal to id
      - answers each explorer row with key equal to id
      - answers an edit with key equal to id
      - answers a deprecation with key equal to id
      - answers an archive with key equal to id
      - answers a restore with key equal to id
      - 'copies under the key given, answering id and key equal'
      - 'copies under the id given, answering id and key equal'
      - 'refuses id and key that differ, 400, naming both'
      - 'refuses a duplicate naming neither id nor key, 400'
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/e2e/eligibility-definition-key-alias.e2e.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.
---

# Eligibility definition key alias 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.