---
id: TST-PFM-INT-585
title: work backoff
kind: unit
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/unit/services/work-backoff.spec.ts
implements:
  - ATS-PFM-INT-014-04
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Pure test fixtures owned by the test process.
evidence:
  - 'services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts'
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#waits 1 minute, 5,
      30, 2 hours and 6 hours between the six attempts
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#stops after the
      sixth attempt
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#stops at once for a
      class no retry fixes
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#retries an unknown
      outcome, whose consumers deduplicate
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#retries an adapter
      error on every attempt, never counting it across them
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#names the next
      attempt
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#pauses at fifty
      consecutive dead deliveries
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#fires above 1 % of
      an endpoint’s hour
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#waits for enough
      requests before judging the share
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#finds the consumer
      of an exact type
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#finds the consumer
      of a prefix
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#finds nobody for a
      type no consumer takes
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#posts to the
      consume route the integration client serves, in the batch’s tenant
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#reads each event’s
      outcome from a service function’s answer
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#retries every event
      of a refused answer
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts#retries every event
      of an answer that is not JSON
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/integrations/tests/unit/services/work-backoff.spec.ts'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# work backoff

## Verification Boundary

This unit suite exercises work backoff. 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

Pure cases do not establish database constraints, deployed authorization or provider effects.

## Real Dependencies and Test Doubles

The suite evaluates its imported functions with controlled inputs. Its source records the fixture and substitution boundary.

## Must Not Be Doubled

The function under test and its result checks must execute. Replacing them with expected answers provides no proof.