---
id: TST-PFM-ELG-418
title: Eligibility condition types table 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/db/eligibility-condition-types.table.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/db/eligibility-condition-types.table.integration.spec.js
    cases:
      - modules/eligibility/db/eligibility-condition-types.table.ts
      - accepts a well-formed registration with no former keys
      - 'refuses a second row of the same key, by the primary key'
      - 'refuses a key without its application part, by the key check'
      - >-
        accepts a key of three segments with camelCase names, the rule grammar’s
        <app>.<area>.<name>
      - 'refuses a key of four segments, by the key check'
      - 'refuses a segment that starts with a capital, by the key check'
      - 'refuses a status outside the three, by the status check'
      - 'refuses declaration version zero, by the version check'
      - 'refuses a declaration that is not an object, by the declaration check'
      - >-
        refuses a type that lists its own key among its former keys, by the
        former keys check
      - 'refuses more than ten former keys, by the former keys check'
      - is read in one tenant
      - is read the same in another tenant
      - 'is read with no tenant at all, because no policy confines it'
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/db/eligibility-condition-types.table.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 table 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.