---
id: TST-PFM-ELG-439
title: Eligibility explorer 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/model/explorer.integration.spec.js
implements:
  - ATS-PFM-ELG-002-03
  - ATS-PFM-ELG-002-06
  - ATS-PFM-ELG-002-07
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/model/explorer.integration.spec.js
    cases:
      - >-
        answers a definition with its usage counts and every column the record
        carries
      - answers zero counts for a definition nobody uses
      - >-
        lists the tenant’s definitions in key order, and none of another
        tenant’s
      - filters by status
      - filters by owner and by reuse
      - filters by a condition type a draft or published version uses
      - matches the text in the name without regard to case
      - takes a percent sign in the text literally rather than as a wildcard
      - 'pages by the key, the cursor resuming after the last record'
      - answers the version it last published and its draft
      - answers its usage counts
      - answers no published version and no draft for a definition created bare
      - 'refuses a key the tenant does not have, 404'
      - >-
        counts the draft reference as well as the published one in the
        definition’s overview
      - counts the same number in the explorer’s row
      - is the number the archive refusal names
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/model/explorer.integration.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 explorer 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.