---
id: TST-PFM-DJE-120
title: Contact update versions
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/contact-update-versions.integration.spec.js
implements:
  - ATS-PFM-DJE-004-04
  - ATS-PFM-DJE-006-01
  - ATS-PFM-DJE-006-04
  - ATS-PFM-DJE-006-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/contact-update-versions.integration.spec.js
assertion_inventory:
  - 'a validated bulk contact update: a colleague edits between the preview and the apply'
  - 'freezes the version of each of the three contacts on the validated job, by item position'
  - skips the contact that changed after the validation as a named conflict
  - leaves the colleague’s edit as they made it
  - >-
    applies the contact whose colleague made the very change the job asks for, rather than calling
    it a conflict
  - applies the contact nobody touched
  - counts the conflict apart from the two applied contacts
  - >-
    offers the revalidation of conflicts on the finished job, to the holders of the keys its route
    requires
  - 'answers the revalidation of a job that does not exist as not found, as every other action does'
  - >-
    makes the revalidation a new validation of the one conflicted contact, linked to the job it
    corrects
  - >-
    captures, on the revalidation, the version the colleague’s edit left, so it can be applied or
    abandoned from what is on screen
  - leaves the colleague’s edit untouched by the revalidation itself
  - 'refuses to revalidate the revalidation itself, which has not finished, by the engine’s code'
  - 'does not offer a retry of the finished job, whose only unapplied contact is a conflict'
  - refuses a retry of the finished job rather than writing over the edit
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Contact update versions

## 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 contact update versions. 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.