---
id: TST-PFM-INT-537
title: event router
kind: integration
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/integrations/tests/integration/services/events/event-router.integration.spec.js
implements:
  - ATS-PFM-INT-015-01
  - ATS-PFM-INT-015-02
  - ATS-PFM-INT-015-05
  - ATS-PFM-INT-015-06
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/integrations/tests/integration/services/events/event-router.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#replaces
      what a principal registered before, whole
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#invokes
      each consumer once for the batch, as platform, at the consume route of the batch’s tenant
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#records
      an event every consumer handled or ignored as delivered, to each of them
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#backs
      off an event a consumer asked to retry, queuing its next attempt a minute out
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#dead-letters
      an event after six attempts of retries
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#retries
      every event of a consumer whose invoke failed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#records
      an event no consumer takes as no_consumer, invoking nobody
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#lists
      the events nobody took for Rhythm HQ, across tenants
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js#does
      nothing for a message of an attempt already made
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/events/event-router.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# event router

## Verification Boundary

This database and service suite exercises event router. 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.