Rhythm 2.0 Specifications

Appearance

ATS-COM-FUL-012Prepare an order's goods for dispatch: Acceptance Test Set

Markdown

ATS-COM-FUL-012

Prepare an order's goods for dispatch: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-COM-FUL-012

KindAcceptance test setProduct areaCommerceModuleFulfillment, Shipping and InventoryRevision1

Read atservices-commerce c8b66a98react-console baf6dae3

Test Scenarios

8 scenarios proving CAP-COM-FUL-012; 6 bound to an existing test.

01 Shipment creation gathers only unassigned unitsapinegativetest
Proves
BR-CAP-COM-FUL-012-01
Preconditions
An order has three picked units at a warehouse.
Steps
Create its shipment and request another without new units.
Expected
The first shipment contains the contiguous three-unit range and saved destination and charge; the next request fails.
Data
Fixtures for shipment creation gathers only unassigned units.
Bound to
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#makes the shipment from the order’s three picked units as one line (units 0..2) at the warehouse, numbered, addressed from the order, charged what the order paid, on the strategy’s carrier and service
services-commerce:modules/shipping/tests/e2e/shipping.e2e.spec.js#refuses a third wave: nothing is left to ship (409 nothing_to_ship)
Source
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#makes the shipment from the order’s three picked units as one line (units 0..2) at the warehouse, numbered, addressed from the order, charged what the order paid, on the strategy’s carrier and service
02 Replenishment enables a later shipping waveapitest
Proves
BR-CAP-COM-FUL-012-02
Preconditions
Three of five ordered units are ready and two are backordered.
Steps
Dispatch the first wave, receive stock and create the next shipment.
Expected
The replenished units become the second shipment and are picked during creation.
Data
Fixtures for replenishment enables a later shipping wave.
Bound to
services-commerce:modules/shipping/tests/e2e/shipping.e2e.spec.js#makes the first wave of the three picked units (0..2), charged what the order paid, and walks it to the handoff
services-commerce:modules/shipping/tests/e2e/shipping.e2e.spec.js#fills the two backorders at the receipt, and the second wave picks the filled units at its creation (3..4) and ships them
services-commerce:modules/shipping/tests/e2e/shipping.e2e.spec.js#completes the order’s shipping: every unit shipped, every obligation completed, the shelf down five, the cost facts emitted per wave
Source
services-commerce:modules/shipping/tests/e2e/shipping.e2e.spec.js#makes the first wave of the three picked units (0..2), charged what the order paid, and walks it to the handoff
03 Pickup creation retains collection without carrier costapitest
Proves
BR-CAP-COM-FUL-012-03
Preconditions
The buyer selected pickup for the order.
Steps
Create a shipment.
Expected
It references the collection warehouse without carrier or shipping charge.
Data
Fixtures for pickup creation retains collection without carrier cost.
Bound to
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#makes a pickup shipment of the order at the pick-up warehouse, on no carrier, charged nothing
services-commerce:modules/shipping/tests/e2e/shipping.e2e.spec.js#makes a pickup shipment of the paid order, on no carrier, and refuses its label 409 operation_not_supported
Source
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#makes a pickup shipment of the order at the pick-up warehouse, on no carrier, charged nothing
04 Picking and packing advance released warehouse workapitest
Proves
BR-CAP-COM-FUL-012-04 BR-CAP-COM-FUL-012-05 BR-CAP-COM-FUL-012-06
Preconditions
A shipment is open.
Steps
Release it, form and claim picking work, record picks and pack parcels.
Expected
Picked quantities become parcels with derived weights and the shipment reaches packed state.
Data
Fixtures for picking and packing advance released warehouse work.
Bound to
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#releases the shipment to the floor and lists its line for picking at the bin the ledger names, the shipment picking
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#records the pick: the list line picked, the shipment line picked with its quantity, the shipment picked
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#packs the three units into two parcels, the second weighed from nothing (the shirt has no weight), the line packed, the shipment packed with two packages
services-commerce:modules/shipping/tests/integration/db/shipping-tables.table.integration.spec.js#holds a picked line to its whole quantity and a short one to less, by pick_list_lines_picked_check, and a claimed list to its picker, by pick_lists_claimed_check
services-commerce:modules/shipping/tests/integration/db/shipping-tables.table.integration.spec.js#refuses a package line of nothing, by package_lines_quantity_check, and one naming a line the tenant does not have, by package_lines_shipment_line_fk
Source
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#releases the shipment to the floor and lists its line for picking at the bin the ledger names, the shipment picking
05 Short picking creates an actionable SKU findingapiproposed
Proves
BR-CAP-COM-FUL-012-05
Preconditions
A three-unit pick line yields only two units.
Steps
Record the actual picked quantity.
Expected
The line is short and its finding identifies the SKU and picking work.
Data
Fixtures for short picking creates an actionable SKU finding.
Source
services-commerce:modules/shipping/tests/integration/db/shipping-tables.table.integration.spec.js#holds a picked line to its whole quantity and a short one to less, by pick_list_lines_picked_check, and a claimed list to its picker, by pick_lists_claimed_check
06 Shipment cancellation retains the underlying orderapinegativetest
Proves
BR-CAP-COM-FUL-012-08
Preconditions
Fixtures contain a labelled shipment and completed collection.
Steps
Cancel each shipment.
Expected
The first loses its labels and shipment assignment while retaining order ownership; collected work rejects cancellation.
Data
Fixtures for shipment cancellation retains the underlying order.
Bound to
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#refuses a second handover (not packed any more) and the cancellation of a collected shipment
Source
services-commerce:modules/shipping/tests/integration/services/fulfillment/shipping-flow.integration.spec.js#refuses a second handover (not packed any more) and the cancellation of a collected shipment
07 Application credentials cannot rewrite shipment eventsapinegativetest
Proves
BR-CAP-COM-FUL-012-09
Preconditions
Shipment history already contains events.
Steps
Attempt event update, deletion and truncation under the application role.
Expected
Each mutation fails and reads retain chronological history.
Data
Fixtures for application credentials cannot rewrite shipment events.
Bound to
services-commerce:modules/shipping/tests/integration/db/shipping-tables.table.integration.spec.js#lets the application role insert an event and refuses it UPDATE, DELETE and TRUNCATE, 42501
Source
services-commerce:modules/shipping/tests/integration/db/shipping-tables.table.integration.spec.js#lets the application role insert an event and refuses it UPDATE, DELETE and TRUNCATE, 42501
08 Warehouse progression checks mutation authorityapinegativeproposed
Proves
BR-CAP-COM-FUL-012-11
Preconditions
A reader and ordinary warehouse clerk are available.
Steps
Exercise shipment creation, release and cancellation for both.
Expected
The reader cannot write and the clerk lacks administrator cancellation authority.
Data
Fixtures for warehouse progression checks mutation authority.
Source
services-commerce:aws/commerce.service.ts:ShipmentsPermissions

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software