---
id: TST-PFM-ELG-386
title: Eligibility rules list checks
kind: browser-lifecycle
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/eligibility-rules-list.mock.spec.ts
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 5
isolation: One browser context with fixture responses.
evidence:
  - provenance: test
    source: 'react-console:e2e/mock/eligibility-rules-list.mock.spec.ts'
    cases:
      - >-
        the Configuration menu opens the list with the standard toolbar and
        columns
      - >-
        rules set just for one thing are not in the library until Show Private
        lists them with their owner
      - 'About, Used By, the search and Show Inactive narrow the list'
      - >-
        Archive is refused while a binding follows the rule; an unused rule is
        archived and restored
      - Select offers Archive and Restore for the rules chosen
      - Add Eligibility Rule and a rule's name open the full-page editor
      - >-
        the old /eligibility URLs redirect to the Configuration routes, the rest
        of the path kept
      - 'somebody who may only read sees no Add, Archive or Select'
  - provenance: documented
    source: 'react-console:e2e/mock/eligibility-rules-list.mock.spec.ts: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 rules list checks

## Verification Boundary

This suite checks console presentation against controlled responses. It cannot establish server enforcement.

## 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. Mocked responses do not establish service, database or permission behavior.

## Real Dependencies and Test Doubles

Console request responses use the suite’s mock handlers. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

The console component and user interaction under test remain real; substituting them defeats the presentation check.