---
id: TST-PFM-DJE-166
title: Records by source key
kind: api-lifecycle
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-platform
files:
  - modules/data-jobs/tests/e2e/records-by-source-key.e2e.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
isolation: >-
  Suite-owned fixture records, job identifiers and workspace contexts; teardown removes the fixture
  data.
evidence:
  - 'services-platform:modules/data-jobs/tests/e2e/records-by-source-key.e2e.spec.js'
assertion_inventory:
  - the lookup by source key of custom field definitions (end to end)
  - in the tenant taking its initial data import
  - is refused the ordinary definition read 403 TenantUnavailable (premise)
  - 'is served the lookup, answering the definition by its key and its record id'
  - reports the key nothing loaded as missing
  - 'who may ask, and how much'
  - refuses 403 permission_missing a caller who may read custom fields but not read a job of them
  - 'refuses 400 a lookup of more than a hundred keys, naming source_keys'
  - answers the customer’s other tenant none of this tenant’s keys
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Records by source key

## Verification Boundary

The suite checks requests through the local production dispatcher and signed caller evaluation. 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.