---
id: TST-PFM-OPS-072
title: Jobs
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: >-
  The prepared local test database and suite-owned identifiers; existing hooks control rollback or
  cleanup.
evidence:
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js at
    ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: This existing engineering suite is registered without claiming a complete specification scenario.
assertion_sources:
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#made a
    pending job of customer tests with no tenant
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#made a
    running job of tenant tests
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#made a
    settled job of each terminal status
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#made
    the failed job for another customer, which is what puts it outside a tests caller’s scope
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#answers
    the jobs of the caller’s scope through Platform’s own view, most recently active first
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#answers
    each job as the view projects it
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#answers
    the execution handle of a job that was started
  - >-
    services-platform:modules/jobs/tests/integration/services/persistence/jobs.integration.spec.js#narrows
    the answer to the statuses the filter names
---

# Jobs

## Verification Boundary

This suite exercises background work through production operations against the local database. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks exercise jobs within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. No complete specification scenario is attributed to this suite yet.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database and production operations under test are real. Execution startup or probing uses a test channel where the suite declares one.

## Must Not Be Doubled

The persistence operations, database constraints and reads under assertion remain real.