---
id: TST-PFM-ELG-444
title: Eligibility condition types checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/eligibility/tests/integration/services/persistence/condition-types.integration.spec.js
implements: []
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/integration/services/persistence/condition-types.integration.spec.js
    cases:
      - >-
        stores a registration active, stamped with the execution’s instant as
        its registration
      - >-
        replaces a registration of the same key, moving its version and its
        instant
      - >-
        folds the type it renames into the new registration, so the old key has
        no row of its own
      - refuses a key that another type lists as a former key
      - >-
        refuses a former key that another application’s type holds, and leaves
        that type
      - refuses a key that is not <application>.<name>
      - refuses a declaration that is not a JSON object
      - deprecates and then withdraws a type
      - >-
        refuses to bring a withdrawn type back by marking it, and leaves it
        withdrawn
      - refuses to mark a key nobody registered
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/persistence/condition-types.integration.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 condition types 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 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. Checks beyond the file’s reachable assertions remain unverified, including production configuration.

## 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 module behavior under assertion, transaction boundary and database constraint being checked remain real. Fixture setup cannot stand in for the asserted write or refusal.