---
id: TST-PFM-INT-561
title: integration executions queries
kind: integration
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - >-
    modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.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: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - >-
    services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      one execution by id with every column mapped
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      nothing of another tenant’s execution
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      an execution’s attempts in order, each mapped
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      the stored answer of a settled execution
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#lists
      the connection’s executions newest first
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#pages
      the list by keyset, resuming after the last record
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#filters
      by status, capability and subject
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#lists
      the unknown executions due a lookup, oldest due first, by keyset
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#lists
      none of them before their lookup is due
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#lists
      the executions needing attention, oldest first
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#counts
      the backlog: the unknown executions due, and those needing attention
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#lists
      the executions in flight, oldest first, each mapped, never a settled one
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#pages
      the executions in flight by keyset, resuming after the position given
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      none of them in another tenant
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      an execution’s latest attempt, every column mapped
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js#reads
      no latest attempt of an execution never attempted
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/persistence/integration-executions.queries.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# integration executions queries

## Verification Boundary

This database and service suite exercises integration executions queries. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.