---
id: TST-PFM-OPS-074
title: Cross service 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/snapshots/cross-service-jobs.integration.spec.js
implements:
  - ATS-PFM-OPS-007-01
  - ATS-PFM-OPS-007-02
  - ATS-PFM-OPS-007-03
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/snapshots/cross-service-jobs.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/snapshots/cross-service-jobs.integration.spec.js#holds
    a root of exactly the columns the roots view answers, the subject aside
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#holds
    steps of exactly the columns the steps view answers, the kind aside
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#holds
    events of exactly the columns the events view answers, the kind aside
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#is
    of a kind Platform publishes no family for, which is what makes it another macroservice’s
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#finds
    the schema that publishes the three views, beside Platform’s own
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#does
    not find a schema that holds the same job and publishes no view
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#lists
    the merge job, which no Platform family holds
  - >-
    services-platform:modules/jobs/tests/integration/services/snapshots/cross-service-jobs.integration.spec.js#answers
    the whole summary of the merge job, mapped as every other job’s is
---

# Cross service 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 publish scratch service views and compare discovery, ordering, scope and snapshots across service boundaries. 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.