---
id: TST-COM-ORD-044
title: Checkouts read
kind: integration
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/checkout/tests/integration/services/persistence/checkouts.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: 2
isolation: The suite creates its own test workspace records and removes them using the fixture cleanup.
evidence:
  - provenance: test
    source: >-
      services-commerce:modules/checkout/tests/integration/services/persistence/checkouts.queries.integration.spec.js
    test_cases:
      - 'answers the checkout whole, every column mapped, its item with its columns'
      - 'finds the buyer’s open cart in the store, and the storeless one for no store'
      - 'lists the open checkouts past their expiry, oldest first, never the abandoned one'
      - >-
        answers, across tenants and in no tenant, every expired open checkout’s tenant and id, oldest expiry
        first
      - 'answers no checkout at all to a read in no tenant without the flag: the policies fail closed'
      - 'refuses the cross-tenant read inside another transaction, so the flag never outlives its own'
      - 'reads a checkout locked for update inside a transaction, and refuses the lock outside one'
      - 'answers undefined for another tenant’s checkout, and no events of it'
scenario_coverage: []
dependency_evidence:
  provenance: test
  source: >-
    services-commerce:modules/checkout/tests/integration/services/persistence/checkouts.queries.integration.spec.js
  declared_by_test: 'PostgreSQL, the persistence service, the execution context under `rhythm_commerce_app`. Doubled: nothing.'
---

# Checkouts read

## Verification Boundary

The suite exercises persistence or workflow operations against the local integration database.

## What This Suite Proves

The registered cases check checkouts read with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

## What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised Commerce persistence or workflow code are real. Remote service records, clocks and transports follow the suite’s fixtures.

## Must Not Be Doubled

The database constraints, role restrictions, locks and transactions exercised by this suite must use PostgreSQL.