---
id: TST-COM-FUL-069
title: Operations
kind: api-lifecycle
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/operations/tests/e2e/operations.e2e.spec.js
implements:
  - ATS-COM-FUL-007-05
  - ATS-COM-FUL-007-07
  - ATS-COM-FUL-008-01
  - ATS-COM-FUL-008-03
  - ATS-COM-FUL-008-10
  - ATS-COM-FUL-008-11
  - ATS-COM-FUL-009-07
  - FAS-COM-FUL-02-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: modules/operations/tests/e2e/operations.e2e.spec.js
    test_titles:
      - >-
        lists the finding the reconciler raised about the unbilled order, filtered by kind, state
        and order, and never another tenant’s
      - >-
        summarizes the counts by kind and state, and answers one finding whole, 404 for another
        tenant’s
      - >-
        refuses the queue to a portal member and the interventions to a reader (403), and a body
        without a reason (400)
      - >-
        acknowledges then resolves the finding, with the interventions logged, the order’s history
        and the audit events recorded
      - >-
        lists the order’s adjustments and the failed ones, answers one with its steps, and refuses a
        query naming neither an order nor a state
      - >-
        retries the failed adjustment on its route: the refund alone re-sent, completed; a reader is
        refused
      - >-
        resolves the other failed adjustment offline on its route, with its exception, and refuses a
        repeat
    scenario_anchors:
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#lists the order’s
        adjustments and the failed ones, answers one with its steps, and refuses a query naming
        neither an order nor a state
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#retries the failed
        adjustment on its route: the refund alone re-sent, completed; a reader is refused
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#resolves the other
        failed adjustment offline on its route, with its exception, and refuses a repeat
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#acknowledges then
        resolves the finding, with the interventions logged, the order’s history and the audit
        events recorded
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#refuses the queue to a
        portal member and the interventions to a reader (403), and a body without a reason (400)
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#lists the finding the
        reconciler raised about the unbilled order, filtered by kind, state and order, and never
        another tenant’s
      - >-
        services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#summarizes the counts
        by kind and state, and answers one finding whole, 404 for another tenant’s
      - 'services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js'
---

# Operations

## Verification Boundary

This suite calls the composed local HTTP handler over the prepared database. It checks operations through request contracts and the enforcing security boundary.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Local handler execution does not establish deployed routing, queue delivery or browser behavior. It also supplies no latest result until a qualification run records one.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Signed local security contexts and the composed handler exercise the request boundary. Accounting command responses use the suite’s fixture port. Time-sensitive cases use a controlled clock where the source fixture supplies one.

## Must Not Be Doubled

Keep the composed handler, permission enforcement, request validation and database writes real when claiming this local API coverage. Scripted financial, queue or carrier outcomes must remain visibly separate from deployed integration evidence.