---
id: TST-COM-ORD-040
title: Checkout expiry sweeper
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/checkout/checkout-sweeper.integration.spec.js
implements:
  - ATS-COM-ORD-001-07
  - ATS-COM-ORD-011-06
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/checkout/checkout-sweeper.integration.spec.js
    test_cases:
      - >-
        answers what it did: the three expired open checkouts of both tenants found and abandoned, none
        skipped
      - >-
        abandoned each expired open checkout in its own tenant, with the system as the actor and expired as
        the reason
      - 'left the live, the unexpiring, the abandoned and the placed checkouts as they were'
      - finds nothing on a second run
      - >-
        takes at most the limit, oldest expiry first, and leaves the rest to the next run; a cancelled
        checkout is not found
scenario_coverage:
  - scenario: ATS-COM-ORD-001-07
    test_cases:
      - >-
        abandoned each expired open checkout in its own tenant, with the system as the actor and expired as
        the reason
      - >-
        takes at most the limit, oldest expiry first, and leaves the rest to the next run; a cancelled
        checkout is not found
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
  - scenario: ATS-COM-ORD-011-06
    test_cases:
      - >-
        abandoned each expired open checkout in its own tenant, with the system as the actor and expired as
        the reason
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
dependency_evidence:
  provenance: test
  source: >-
    services-commerce:modules/checkout/tests/integration/services/checkout/checkout-sweeper.integration.spec.js
  declared_by_test: >-
    PostgreSQL (the sweep policy of migration `20261017185111`), the persistence services, the execution
    contexts under `rhythm_commerce_app`. Doubled: nothing.
---

# Checkout expiry sweeper

## Verification Boundary

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

## What This Suite Proves

The registered cases check checkout expiry sweeper 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.