---
id: TST-PFM-ELG-453
title: Eligibility dependencies queries 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/dependencies.queries.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/dependencies.queries.integration.spec.js
    cases:
      - >-
        reads a version’s dependencies with their detail, in kind and target
        order
      - >-
        answers the versions that reference a definition, joined to their
        definition, in key order, and none of another tenant
      - >-
        answers the versions that use a condition type, and none of another
        tenant
      - answers nothing for a condition type no version uses
      - answers no dependencies for a version that records none
      - answers no dependents for a definition nothing references
      - >-
        counts the versions that reference it from a draft as well as from a
        published version (DEF-ELIG-0137)
      - >-
        lists each reference with the status of the version it comes from, in
        key order
      - counts exactly what the archive refusal counts
      - answers nothing for a definition nobody references
      - does not count a definition’s reference to itself
      - answers nothing for no definitions
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/persistence/dependencies.queries.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 dependencies queries 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 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.