---
id: TST-PFM-DJE-129
title: Records by source key
kind: integration
product_area: platform
module: data-job-engine
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-crm
files:
  - modules/data-jobs/tests/integration/services/jobs/records-by-source-key.integration.spec.js
implements:
  - ATS-PFM-DJE-015-01
  - ATS-PFM-DJE-015-02
  - ATS-PFM-DJE-015-03
  - ATS-PFM-DJE-015-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Suite-owned fixture records, job identifiers and workspace contexts; teardown removes the fixture
  data.
evidence:
  - >-
    services-crm:modules/data-jobs/tests/integration/services/jobs/records-by-source-key.integration.spec.js
assertion_inventory:
  - records read back by source key
  - what the import left (premises)
  - maps both contact keys and the organization key to records
  - contacts
  - 'answers each key found with its record id, in the order the keys were asked'
  - answers each record exactly as the ordinary read of one contact does
  - carries the owned collections the import wrote
  - carries the custom fields the import wrote
  - reports the key nothing loaded as missing
  - organizations
  - answers the organization exactly as the ordinary read of one organization does
  - carries its phone numbers and its custom field
  - 'looks a key up under its own object type only: a contact key is not an organization'
  - a configuration record and a crosswalk row whose record is gone
  - answers the address type exactly as its ordinary read does
  - 'reports a key whose record the tenant does not have as missing, never as a record'
  - the limit
  - 'refuses more than 100 keys by InvalidRequest, naming the limit'
  - 'answers exactly 100 keys, the most a lookup may name'
  - tenant isolation
  - answers none of the first tenant’s keys in the other tenant
  - 'answers the other tenant’s own record for a key both tenants hold, never the first tenant’s'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Records by source key

## Verification Boundary

The suite checks the production service or shared engine against its database fixture. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise records by source key. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

Local execution does not establish deployed queue, storage or service behavior. Independent test cases do not establish a complete cross-feature process.

## Real Dependencies and Test Doubles

The owning service exercises production persistence and domain behavior against real Postgres. The fixture supplies caller contexts; queue delivery, storage and external calls are doubled where the file installs a test port.

## Must Not Be Doubled

The database effects, security context and production operation under examination remain real. Their outcomes cannot be replaced with canned success responses.