---
id: TST-PFM-INT-460
title: rule handlers
kind: api-lifecycle
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - modules/extensions/tests/e2e/rule-handlers.e2e.spec.js
implements:
  - ATS-PFM-INT-017-05
  - ATS-PFM-INT-017-10
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - 'services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js'
test_cases:
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#refuses a rule its point’s
      contract refuses as 400, naming each problem by its path and code
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#saves a rule that fits its
      point’s current version
    provenance: test
  - source: 'services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#member elsewhere'
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#answers the Northeast
      member’s example with 15 percent of the package off, in minor units, in quote mode
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#answers the member
      elsewhere with rule_not_applicable
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#records each run as a test
      invocation of the handler
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#publishes the version’s
      neutral output on the point’s read
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js#answers the member
      elsewhere with the neutral output instead of rule_not_applicable
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/extensions/tests/e2e/rule-handlers.e2e.spec.js'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# rule handlers

## Verification Boundary

This database and service suite exercises rule handlers. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.