Complete business flow testing

End-to-End Business Verification

When to Use

Use when designing test plans, writing automated integration tests, or reviewing CRM/ERP implementations.

Test the Complete Business Workflow, Not Isolated CRUD Forms

Testing that POST /quotes inserts a row and PATCH /quotes/:id updates a field proves almost nothing about an ERP/CRM system. Every business feature must be verified across its complete multi-step lifecycle and exception paths:

1. End-to-End Happy & Partial-Execution Flows

Walk a realistic business transaction through all connected modules in an automated integration test:

• Example (Quote $\rightarrow$ Approval $\rightarrow$ Order $\rightarrow$ Partial Fulfillment):
  1. Create a draft Quote with 2 line items (Item A: 10 pcs @ 100 EUR, Item B: 5 pcs @ 200 EUR) and a discount that triggers manager approval.
  2. Verify the requester cannot self-approve (403) and cannot convert an unapproved quote to an order.
  3. Approve the quote as an authorized manager; verify editing the quote amount now invalidates the approval or is blocked.
  4. Convert the approved quote into a SalesOrder; assert line prices, currency, customer references, and quote lineage match 100%, and catalog price changes after this point do not mutate the order.
  5. Verify inventory reservation: reserved_qty increases by 10 and 5, and available_to_promise decreases accordingly.
  6. Execute a Partial Fulfillment (ship 6 pcs of Item A and 0 pcs of Item B):
     • Assert Order fulfillment status transitions to partially_fulfilled.
     • Assert line 1 shows ordered: 10, fulfilled: 6, remaining: 4, on_hand drops by 6, and remaining reserved is 4.
  7. Execute the remaining fulfillment (or cancel/return the unshipped remainder) and assert final state and inventory balances reconcile to the exact unit and cent.

2. Mandatory Exception, Reversal & Contention Scenarios

Always test the real-world operational exceptions:

• Insufficient Stock / Concurrent Oversell: Two concurrent orders competing for the last 5 units in stock $\rightarrow$ exactly one succeeds (or backorders according to business policy) and available_qty never drops below zero unintentionally.
• Partial Cancellation & Returns (RMA): Cancelling remaining unshipped lines on a partially fulfilled order, or returning 2 defective units from a delivered shipment $\rightarrow$ verify stock restoration/quarantine and credit eligibility.
• Duplicate Merge & Sync Idempotency: Re-running an import or webhook delivery twice, or merging two duplicate customer accounts that both have open opportunities and orders $\rightarrow$ verify zero lost history and zero double-counted revenue.