---
id: TST-COM-FUL-011
title: Data job worker
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js
implements:
  - ATS-COM-FUL-020-05
  - FAS-COM-FUL-05-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js
    test_titles:
      - >-
        claims the one batch, publishes one message naming the tenant, the job and the batch, and
        deletes the queue row
      - 'runs the batch as the submitter, applies its item and acknowledges the message'
      - 'applies nothing on a second delivery of the same message, and acknowledges it still'
      - 'is reported unreadable and left for the dead-letter queue, never retried as work'
      - >-
        acknowledges the message as access_revoked and fails the job whole with that code, nothing
        left on the queue
    scenario_anchors:
      - >-
        services-commerce:modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js#claims
        the one batch, publishes one message naming the tenant, the job and the batch, and deletes
        the queue row
      - >-
        services-commerce:modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js#runs
        the batch as the submitter, applies its item and acknowledges the message
      - >-
        services-commerce:modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js#applies
        nothing on a second delivery of the same message, and acknowledges it still
      - >-
        services-commerce:modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js#is
        reported unreadable and left for the dead-letter queue, never retried as work
      - >-
        services-commerce:modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js#acknowledges
        the message as access_revoked and fails the job whole with that code, nothing left on the
        queue
      - >-
        services-commerce:modules/data-operations/tests/integration/services/queue/data-job-worker.integration.spec.js
---

# Data job worker

## Verification Boundary

This suite checks data job worker against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Queue publication uses the suite’s recording or scripted publisher.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.