---
id: TST-PFM-INT-480
title: events dummy
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/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js
implements:
  - ATS-PFM-INT-013-03
  - ATS-PFM-INT-013-04
  - ATS-PFM-INT-013-05
  - ATS-PFM-INT-014-02
  - ATS-PFM-INT-015-03
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/e2e-adapters/events-dummy.adapters.spec.js'
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#answers the
      administrator its public URL and, the first time, its secret
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#never
      answers the secret again
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is answered
      received at once
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is verified
      and processed by the dummy into a payments.payment.updated event
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#reaches
      Accounting’s consumer, which acknowledges it
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is ignored
      as a duplicate when the provider sends it again
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is rejected
      when its body was tampered with after signing
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is rejected
      when its signed timestamp is older than the five minutes the dummy tolerates (a replay)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is answered
      inline with the dummy’s token and its signature under the endpoint’s secret
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#creates the
      subscription through the console route
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#answers the
      change-events framework one result per event, succeeded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is received
      by the dummy, with the projection’s changed fields and never a system column
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#is
      acknowledged by the dummy’s receiver and recorded delivered
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js#reaches the
      consumer of the application that invoked it, carrying the response
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/integrations/tests/e2e-adapters/events-dummy.adapters.spec.js'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# events dummy

## Verification Boundary

This database and service suite exercises events dummy. 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.