Receiving Edge Case Guide

Overview

This guide lists edge cases for Receiving module testing. Use it during QA to find problems before go-live.

Module: Receiving Total Edge Cases: 12 Critical: 4 High: 5 Medium: 3

Severity Definitions

1. Critical Write Sequences

EC-001: PO Header Before Detail

Severity: CRITICAL Source: data-integrity.md

What Happens: PO header must exist before adding lines. If order is wrong, lines are orphaned.

Test Steps:

1. Try to add line to non-existent PO
2. System should reject

Expected: Error message, no orphan records.

EC-002: LP Creation Before Inventory

Severity: CRITICAL Source: data-integrity.md

What Happens: License plate record must exist before inventory is added. Wrong order causes lost inventory.

Test Steps:

1. Complete a receive
2. Check LP record exists
3. Check inventory record exists
4. Verify LP was created first

Expected: LP created before inventory in all cases.

EC-003: Inventory Update After Receipt

Severity: CRITICAL Source: data-integrity.md

What Happens: Receipt record must commit before inventory updates. If receipt fails, inventory should not change.

Test Steps:

1. Start a receive
2. Force error mid-process
3. Check inventory did not change

Expected: No partial updates. All or nothing.

2. Race Conditions

EC-004: Two Users Same PO

Severity: CRITICAL Source: data-integrity.md

What Happens: Two users open same PO at same time. Both try to receive same line.

Test Steps:

1. User A opens PO-001
2. User B opens PO-001
3. User A receives line 1
4. User B tries to receive line 1

Expected: User B gets lock warning. Cannot double-receive.

EC-005: PO Close During Receive

Severity: HIGH Source: data-integrity.md

What Happens: User is receiving. Someone closes the PO in another session.

Test Steps:

1. User A starts receiving PO-001
2. User B closes PO-001
3. User A tries to continue

Expected: User A gets warning. Partial work is saved.

EC-006: Rapid Label Print

Severity: HIGH Source: technical-questions.md

What Happens: User presses F6 multiple times quickly. May print duplicate labels.

Test Steps:

1. Complete a receive
2. Press F6 three times fast
3. Count labels printed

Expected: Only one label per LP. Duplicates prevented.

3. State Machine Edge Cases

EC-007: PO Status Transitions

Severity: HIGH Source: business-rules.md

What Happens: PO moves through states: Open → Partial → Complete → Closed. Invalid transitions should be blocked.

Test Steps:

1. Try to reopen a Closed PO
2. Try to receive against Closed PO
3. Try to skip from Open to Closed

Expected: Invalid transitions rejected.

EC-008: LP Status After Putaway

Severity: HIGH Source: data-integrity.md

What Happens: LP status changes when put away. Should not allow receiving on LP after putaway starts.

Test Steps:

1. Receive items to LP
2. Start putaway
3. Try to add more items to same LP

Expected: System blocks adding to in-progress LP.

4. Integration Failure Scenarios

EC-009: Printer Offline

Severity: HIGH Source: technical-questions.md

What Happens: User completes receive but printer is offline.

Test Steps:

1. Turn off label printer
2. Complete a receive
3. Press F6 to print

Expected: Error message. User can retry. Receive is not lost.

EC-010: Scanner Disconnect

Severity: MEDIUM Source: technical-questions.md

What Happens: Scanner disconnects during barcode entry.

Test Steps:

1. Start UCI receive
2. Unplug scanner
3. Check screen state

Expected: User can reconnect or type manual. No data loss.

5. Boundary Conditions

EC-011: Maximum Quantity

Severity: MEDIUM Source: business-rules.md

What Happens: User enters very large quantity. System must handle.

Test Values:

EC-012: Date Boundary

Severity: MEDIUM Source: business-rules.md

What Happens: User enters date exactly on boundary (e.g., exactly 90 days out).

Test Steps:

1. Set customer rule to 90 days
2. Enter date exactly 90 days out
3. Check if warning or accept

Expected: Exactly 90 = Accept (green). 89 = Warning (yellow).

6. Recovery Procedures

General Recovery

If something goes wrong:

1. Press F3 to exit
2. Do not turn off terminal
3. Call IT Help Desk
4. Note what you were doing

Emergency Contacts

Test Execution Summary

Sign-Off

Generated by generate-customer-docs skill v1.0.0