---
id: TST-PFM-INT-568
title: webhook worker
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/webhooks/webhook-worker.integration.spec.js
implements:
  - ATS-PFM-INT-013-03
  - ATS-PFM-INT-013-04
  - ATS-PFM-INT-013-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/webhooks/webhook-worker.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#rejects
      a request whose signature does not verify, writing no event
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#hands
      the adapter a presigned URL of the stored body and the endpoint’s secret
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#processes
      a verified request into its integration events, each queued for routing, with the provider subject
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#names
      the Rhythm record and the execution when the execution that created the provider object is found
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#ignores
      a second request with the provider event id of one already processed, pointing at the first
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#ignores
      the same body on the same endpoint within a day when the provider gives no event id
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#processes
      a replayed request again, bypassing deduplication, with replayed_from and new events
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#does
      nothing for a redelivered message of an attempt already made
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#retries
      a classified failure with the async backoff, and records it dead after six attempts
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#records
      a failure no retry can fix dead at once
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js#verifies
      with the previous secret too while the endpoint rotates
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/webhooks/webhook-worker.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# webhook worker

## Verification Boundary

This database and service suite exercises webhook worker. 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.