---
id: TST-COM-FUL-080
title: Shipment events queries
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - >-
    modules/shipping/tests/integration/services/persistence/shipment-events.queries.integration.spec.js
implements:
  - ATS-COM-FUL-012-07
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
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/shipping/tests/integration/services/persistence/shipment-events.queries.integration.spec.js
    test_titles:
      - counts a label’s void intents on its shipment
      - 'counts none for a label with no void intent, though its shipment has others'
      - 'counts only the shipment named: the same label id on another shipment is its own count'
      - 'never counts another tenant’s events: the other tenant’s shipment answers none in the tenant'
      - 'reads the shipment’s history oldest first, the void intents among it'
    scenario_anchors:
      - >-
        services-commerce:modules/shipping/tests/integration/services/persistence/shipment-events.queries.integration.spec.js#reads
        the shipment’s history oldest first, the void intents among it
---

# Shipment events queries

## Verification Boundary

This suite checks shipment events queries against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## 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

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Time-sensitive cases use a controlled clock where the source fixture supplies one.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.