This flagship demo shows RunProof taking a real acceptance criterion, running a fixed SauceDemo flow, and producing a result a visitor can understand without reading raw artifacts.
Flagship site: SauceDemo
Supporting proof: Herokuapp
Supporting proof: Automationexercise
No fourth site in v1
Acceptance Criteria
Source: SauceDemo AC-20
RequirementUsers can finalize their order and receive confirmation.
PreconditionUser must be authenticated as standard_user on inventory page.
1. Navigate to inventoryUser lands on https://www.saucedemo.com/inventory.html.
2. Add one product and open the cartUser clicks the Add to cart button for Sauce Labs Backpack.
3. Start checkoutUser clicks the cart icon, clicks Checkout, and reaches /checkout-step-one.html.
4. Enter customer detailsUser fills first name, last name, and postal code, then clicks Continue.
5. Confirm the orderText Checkout: Overview appears, the user clicks Finish, and Thank you for your order! becomes visible.
What This Proves
Two-minute takeaway
Requirements stay visibleThe visitor sees the exact AC before the run, not just an opaque button.
RunProof executes a real flowThe flagship demo is a real website workflow, not a toy local mock.
Outcome is understandableThe result view compresses run output into verdict, evidence, and next conclusion.