---
id: TST-PFM-QRY-250
title: Platform custom table revalidation
kind: integration
product_area: platform
module: queries
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464
repository: services-platform
files:
  - modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js
implements:
  - ATS-PFM-QRY-005-15
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: 'The suite’s database fixtures, controlled execution contexts and file-owned external dependency seams.'
evidence:
  - >-
    services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js
assertion_bindings:
  - scenario: ATS-PFM-QRY-005-15
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js#checks
        every published version and every version an assignment pins, each once
      - >-
        services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js#writes
        no row at all, because the day’s revalidated row is already there
      - >-
        services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js#never
        writes the statement or a column name into the history
      - >-
        services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js#records
        that it came back, so the history reads as the moments it broke and recovered
      - >-
        services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js#says
        it skipped, and checks nothing
    scope: assertions cited by the scenario
    provenance: test
fixture_seams:
  - >-
    services-platform:modules/queries/tests/integration/services/custom-tables/custom-table-revalidation.integration.spec.js:106
---

# Platform custom table revalidation

## Verification Boundary

The file invokes its service or persistence boundary against local integration fixtures.

## What This Suite Proves

Its assertions check custom table revalidation. The assertion bindings identify the corresponding acceptance examples and retain their original test-title citations.

## What It Does Not Prove

Local execution does not establish deployed queue scheduling, every external provider response or a passing result at the pinned revision.

## Real Dependencies and Test Doubles

The integration fixture and any imported dependency seams define the environment. Database-oriented checks use PostgreSQL; file-owned transport, clock, provider or worker seams isolate the explicitly controlled boundary.

## Must Not Be Doubled

Keep the service or persistence operation whose behavior is asserted real. Database constraints and transactions cannot be replaced by fixture answers when they are the subject of the check.