---
id: TST-COM-ORD-023
title: 'Checkout: what the store sells to the public (D8, end to end)'
kind: api-lifecycle
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/checkout/tests/e2e/checkout-public-sale.e2e.spec.js
implements:
  - ATS-COM-ORD-001-05
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/e2e/checkout-public-sale.e2e.spec.js'
    test_cases:
      - >-
        refuses a portal member opening a checkout with a draft product: 400 product_not_published, naming the
        store, nothing written
      - >-
        refuses a portal member a published product the store does not admit: 400
        product_not_in_store_assortment
      - 'opens the checkout for a published product the store admits, and adds the same product again'
      - 'refuses a portal member adding a draft product to an open checkout, and leaves the checkout as it was'
      - >-
        lets a console user holding commerce.orders.create open a checkout with the draft product and add the
        one outside the assortment
scenario_coverage:
  - scenario: ATS-COM-ORD-001-05
    test_cases:
      - >-
        refuses a portal member opening a checkout with a draft product: 400 product_not_published, naming the
        store, nothing written
      - >-
        refuses a portal member a published product the store does not admit: 400
        product_not_in_store_assortment
      - >-
        lets a console user holding commerce.orders.create open a checkout with the draft product and add the
        one outside the assortment
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
---

# Checkout: what the store sells to the public (D8, end to end)

## Verification Boundary

The suite drives the composed local API dispatcher and its registered routes.

## What This Suite Proves

The registered cases check checkout: what the store sells to the public (D8, end to end) 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.