/wms-testing-patterns

name: wms-testing-patterns
description: "Warehouse Management System testing patterns for inventory operations, pick/pack/ship workflows, wave management, EDI X12/EDIFACT compliance, RF/barcode scanning, and WMS-ERP integration. Use when testing WMS platforms (Blue Yonder, Manhattan, SAP EWM)."
category: enterprise-integration
priority: high
tokenEstimate: 1800
agents: [qe-middleware-validator, qe-contract-validator, qe-sap-idoc-tester, qe-odata-contract-tester]
implementation_status: optimized
optimization_version: 2.0
last_optimized: 2026-02-04
dependencies: [api-testing-patterns, contract-testing, enterprise-integration-testing]
quick_reference_card: true
tags: [wms, warehouse, inventory, edi, pick-pack-ship, blue-yonder, manhattan, sap-ewm, rf-scanning]
trust_tier: 3
validation:
  schema_path: schemas/output.json
  validator_path: scripts/validate-config.json
  eval_path: evals/wms-testing-patterns.yaml

WMS Testing Patterns

<default_to_action> When testing Warehouse Management Systems: 1. VALIDATE inventory accuracy (receipt, putaway, cycle count, adjustments) 2. TEST pick/pack/ship workflows end-to-end (wave release -> shipment confirm) 3. VERIFY EDI message processing (856 ASN, 940 Order, 945 Confirmation, 943/944 Stock) 4. ASSERT RF/barcode scanning flows (scan -> validate -> update -> confirm) 5. EXERCISE allocation and replenishment logic (FIFO, FEFO, lot control) 6. TEST WMS-ERP integration (inventory sync, order status, goods receipt) 7. VALIDATE wave management (wave planning, release, short-pick handling)

**Quick Pattern Selection:**

• Inventory discrepancies -> Cycle count and adjustment tests
• Order fulfillment issues -> Pick/pack/ship workflow tests
• EDI failures -> Message format and acknowledgment tests
• Scanning problems -> RF device simulation tests
• Allocation errors -> Lot control and FIFO/FEFO tests
• Integration gaps -> WMS-ERP sync boundary tests

**Critical Success Factors:**

• WMS accuracy directly impacts customer experience and financial reporting
• Always test both normal and exception flows (short picks, damaged goods, returns)
• EDI testing must cover both syntax validation AND business rule validation

</default_to_action>

Quick Reference Card

When to Use

• Testing WMS platforms (Blue Yonder/JDA, Manhattan Associates, SAP EWM, Oracle WMS)
• Validating inventory transaction accuracy (receipts, picks, adjustments)
• Testing EDI document exchange (X12 856/940/945/943/944, EDIFACT DESADV/ORDERS)
• Verifying RF/mobile scanning workflows
• Testing wave management and allocation logic
• Validating WMS-to-ERP integration (SAP MM/WM, Oracle)

Testing Levels

| Level | Purpose | Dependencies | Speed | |-------|---------|--------------|-------| | Unit Logic | Allocation/replenishment rules | None | Fast | | API Contract | WMS REST/SOAP endpoint contracts | API stubs | Fast | | EDI Validation | Document syntax + business rules | EDI parser | Medium | | Integration | WMS-ERP inventory sync | Full stack | Slower | | E2E Workflow | Complete order fulfillment cycle | WMS + ERP + TMS | Slow |

Critical Test Scenarios

| Scenario | Must Test | Example | |----------|----------|---------| | Receiving | Inbound accuracy | PO receipt with over/under delivery tolerance | | Putaway | Location assignment | Directed putaway by product attributes | | Picking | Wave/batch pick | Multi-order wave with priority allocation | | Packing | Pack verification | Cartonization and weight/dim validation | | Shipping | Carrier assignment | Rate shopping and label generation | | Cycle Count | Inventory accuracy | Blind count vs. guided count reconciliation | | Returns | Reverse logistics | RMA receipt, inspection, disposition | | EDI 856 | ASN generation | Ship-confirm triggers correct ASN to customer | | EDI 940 | Warehouse order | Inbound order creates correct work orders | | Short Pick | Exception handling | Partial allocation with backorder creation |

Tools

• **WMS Platforms**: Blue Yonder WMS, Manhattan WMOS, SAP EWM, Oracle WMS Cloud
• **EDI Testing**: Bots EDI, SPS Commerce Test, Cleo Clarify
• **RF Simulation**: Custom RF emulators, Zebra SDK test harnesses
• **Integration**: SAP PI/PO, MuleSoft, Dell Boomi
• **Monitoring**: Splunk, WMS dashboards, EDI tracking portals

Agent Coordination

• `qe-middleware-validator`: WMS-ERP integration flows and message transformation validation
• `qe-contract-validator`: EDI document contracts and WMS API contracts
• `qe-sap-idoc-tester`: WMS-SAP IDoc validation (WMMBID01, SHPCON)
• `qe-odata-contract-tester`: SAP EWM OData service testing

---

Inventory Transaction Testing

Receipt and Putaway

describe('Inbound Receipt - PO with Lot Control', () => {
  it('receives goods against PO with lot tracking', async () => {
    const receipt = await wms.receive({
      po: 'PO-4500001234',
      item: 'MAT-100',
      quantity: 100,
      lot: 'LOT-2026-001',
      expiryDate: '2027-06-30',
      uom: 'EA'
    });

    expect(receipt.status).toBe('RECEIVED');
    expect(receipt.quantityReceived).toBe(100);
    expect(receipt.lot).toBe('LOT-2026-001');

    // Verify putaway task was created
    const putawayTask = await wms.getTask(receipt.putawayTaskId);
    expect(putawayTask.type).toBe('DIRECTED_PUTAWAY');
    expect(putawayTask.suggestedLocation).toMatch(/^BIN-/);
  });

  it('rejects over-receipt beyond tolerance', async () => {
    // PO line is for 100 EA, tolerance is 10%
    const result = await wms.receive({
      po: 'PO-4500001234',
      item: 'MAT-100',
      quantity: 115, // 15% over, exceeds 10% tolerance
      lot: 'LOT-2026-002'
    });

    expect(result.status).toBe('REJECTED');
    expect(result.reason).toContain('Over-receipt tolerance exceeded');
    expect(result.maxAllowed).toBe(110);
  });

  it('accepts under-receipt and creates remaining open quantity', async () => {
    const result = await wms.receive({
      po: 'PO-4500001234',
      item: 'MAT-100',
      quantity: