---
id: TST-COM-ORD-016
title: The Orders table
kind: unit
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - components/commerce/orders/__tests__/orders-list-screen.test.tsx
implements:
  - ATS-COM-ORD-010-06
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The suite owns its in-memory inputs, scripted responses and rendered component state.'
evidence:
  - provenance: test
    source: 'react-console:components/commerce/orders/__tests__/orders-list-screen.test.tsx'
    test_cases:
      - heads the six columns staff read
      - 'shows the number, the customer, the status, the total and the balance due'
      - opens Order 360 under the buyer from the order number
      - marks a voided order's balance as none rather than zero
      - says so when CRM has no name for the customer
      - writes a foreign currency with its code
      - never says tenant
scenario_coverage:
  - scenario: ATS-COM-ORD-010-06
    test_cases:
      - heads the six columns staff read
      - 'shows the number, the customer, the status, the total and the balance due'
      - opens Order 360 under the buyer from the order number
      - marks a voided order's balance as none rather than zero
      - never says tenant
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
---

# The Orders table

## Verification Boundary

The component suite renders the named screen with controlled adapter results.

## What This Suite Proves

The registered cases check the Orders table 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

Inputs and external responses are controlled in process; this suite establishes no deployed service behavior.

## Must Not Be Doubled

The named contract validation or component behavior under assertion must use its actual implementation.