---
id: TST-PFM-MTD-132
title: quick search archived field
kind: integration
product_area: platform
module: metadata
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js
implements:
  - ATS-PFM-MTD-005-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Prepared integration database and the suite fixture records; fixture teardown restores or removes its own
  rows.
evidence:
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#published
    the configuration’s own generation before the archive (the premise)
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#indexed
    the custom field’s value, which is what the archive has to remove (the premise)
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#searched
    that value in the tier the tenant configured it in (the premise)
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#runs
    the rebuild the archive asked for to success
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#runs
    the rebuild the archive asked for, and no other
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#leaves
    the archived field out of the document’s fields, so a hit no longer carries the value
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#leaves
    the value out of the searched tiers, so nobody finds the record by it any more
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#keeps
    the field the dataset still describes, so the rebuild dropped one field and not the record
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#keeps
    every contact of the tenant live: a field going away tombstones nothing
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#publishes
    the generation the archive targeted as the active one
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#still
    records the field as degraded, which is how the configuration screen explains the empty field
  - >-
    services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#rewrote
    a document for every contact of the type, which is what makes the removal complete
fixture_imports:
  - ../../../../../metadata/services/field-lifecycle/archive-field
  - ../../../../services/configuration/apply-configuration
  - ../../../../services/persistence/index-states
  - ./rebuild-support
test_doubles: []
limitations: []
unmatched_specification: null
binding_assertions:
  - scenario: ATS-PFM-MTD-005-08
    provenance: test
    source:
      - >-
        services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#leaves
        the value out of the searched tiers, so nobody finds the record by it any more
      - >-
        services-platform:modules/quick-search/tests/integration/lifecycle/rebuild/quick-search-archived-field.integration.spec.js#runs
        the rebuild the archive asked for to success
    note: >-
      These references identify the assertions this suite contributes; bindings to additional suites remain
      part of the scenario’s proof.
---

# Quick search archived field

## Verification Boundary

This integration suite checks search after field archival within the local test harness. The registered file and pinned revision define its boundary.

## What This Suite Proves

The bindings identify the detailed or feature scenarios whose outcomes have assertions in this suite. Original case references remain attached to the detailed scenarios so a reviewer can inspect the exact assertion. Assertions are evidence of implemented checks; no execution result is claimed.

## What It Does Not Prove

The register does not establish a current passing run or full specification conformance. Behavior outside the suite’s fixtures and assertions remains unverified.

## Real Dependencies and Test Doubles

The fixture uses PostgreSQL and the imported persistence or API code. The fixture imports identify the setup seams; this register makes no broader claim that dependencies are undoubled.

## Must Not Be Doubled

The operation under examination and its asserted stored outcomes must remain real within the declared harness. A fixture cannot replace the write, refusal or transactional effect that the bound scenario checks.