---
id: TST-PFM-OPS-075
title: Job subject
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/subjects/job-subject.integration.spec.js
implements:
  - ATS-PFM-OPS-006-02
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/subjects/job-subject.integration.spec.js at
    ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: Bindings apply only to the listed specification scenarios.
assertion_sources:
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#answers
    the tenant, named, for a job that names one
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#answers
    the customer, named, for a job that names a customer and no tenant
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#answers
    no subject at all for a job that belongs to neither
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#answers
    the tenant and not the customer when the job names both
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#names
    the subject null, and still answers it, for a tenant that no longer reads
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#names
    the subject null, and still answers it, for a customer that no longer reads
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#answers
    the display name of the user who asked for the job
  - >-
    services-platform:modules/jobs/tests/integration/services/subjects/job-subject.integration.spec.js#answers
    no requester name for a job raised by a system actor, which names no user
---

# Job subject

## 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 job subject within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. The scenario bindings name the attributed outcomes.

## 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.

## Must Not Be Doubled

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