---
id: TST-PFM-QRY-343
title: Platform run with refinement
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/saved-queries/run-with-refinement.integration.spec.js
implements:
  - ATS-PFM-QRY-007-05
  - ATS-PFM-QRY-007-06
  - ATS-PFM-QRY-007-07
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/saved-queries/run-with-refinement.integration.spec.js
assertion_bindings:
  - scenario: ATS-PFM-QRY-007-05
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/saved-queries/run-with-refinement.integration.spec.js#narrows
        to the rows that also meet the refinement’s criteria
      - >-
        services-platform:modules/queries/tests/integration/services/saved-queries/run-with-refinement.integration.spec.js#never
        widens: criteria naming a contact outside the query answer none of it
      - >-
        services-platform:modules/queries/tests/integration/services/saved-queries/run-with-refinement.integration.spec.js#never
        widens: a negated refinement still answers only the query’s rows
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
  - scenario: ATS-PFM-QRY-007-06
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/saved-queries/run-with-refinement.integration.spec.js#answers
        the columns the refinement names instead of the stored ones, over the same rows
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-007-07
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/saved-queries/run-with-refinement.integration.spec.js#refuses
        criteria that ask for a value when run, which only a stored definition may
      - >-
        services-platform:modules/queries/tests/integration/services/saved-queries/run-with-refinement.integration.spec.js#still
        asks for the value: a refinement does not stand in for a required parameter
    scope: assertions cited by the scenario
    provenance: test
fixture_seams: []
---

# Platform run with refinement

## Verification Boundary

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

## What This Suite Proves

Its assertions check run with refinement. 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.