# BigCommerce test plan > Verify the BigCommerce quickstart, reconcile payments and orders, and check the experience your store controls. Source: https://help.boltapp.com/platforms/bigcommerce-test-plan Run this plan after the [BigCommerce Quickstart](/platforms/bigcommerce). These are acceptance criteria, not recorded results. All cases start **Not run**. ## Fixtures and evidence [#fixtures-and-evidence] Use the test store and Bolt Payments sandbox division from the guide, one available physical product, a supported shipping address, and [test cards](/getting-started/test-cards#bolt-payments). Record the app/theme version, date, case ID, Bolt transaction reference, store order ID, amounts and screenshots. Do not record keys, secrets or card details in evidence. Use a fresh cart or purchase for each payment case. Keep the same product/variant fixture; wait for catalog/configuration updates before retesting. Reconcile uncertain outcomes before retrying. Preserve order evidence; do not refund or delete records as routine cleanup. Refund testing is a separate launch case using the [platform refund guidance](/dashboard/refunds). Restore changed permissions and browser network settings after failure tests. Mark **Passed**, **Failed**, or **Blocked** with evidence after execution. Baseline completion requires all applicable setup, checkout, payment and merchant-experience cases to pass. Missing required capabilities are Blocked. Additional launch cases do not imply the quickstart built those features. ## App and Bolt connection [#app-and-bolt-connection] | Test | Input | Steps | Expected output | Result | | ---------------------------- | -------------------------------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | ------- | | BC-01: Sandbox configuration | Sandbox app and test division | 1. Inspect installed app. 2. Review payment keys and configuration mode. | Sandbox app, matching division and Full Bolt Checkout mode; no production credentials. | Not run | | BC-02: Webhook destination | Known test store hash | 1. Open sandbox Webhooks. 2. Compare endpoint with store hash. | Endpoint is populated by the app and points to the intended BigCommerce store. | Not run | | BC-03: Secret placement | Rendered copied theme and source | 1. Inspect script attributes/source. 2. Compare key types. | Only publishable key appears in theme; API key and signing secret remain in payment-method configuration. | Not run | ## Cart integration [#cart-integration] | Test | Input | Steps | Expected output | Result | | ------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ | ------- | | BC-04: Open cart checkout | One item on copied Cornerstone cart page | 1. Select Bolt checkout. 2. Compare item and quantity. | Checkout opens for the current cart and sandbox division. | Not run | | BC-05: Quantity refresh | Cart quantity changed from 1 to 2 | 1. Change quantity. 2. Wait for total update. 3. Open checkout. | Checkout quantity and total reflect the updated cart, with no stale price. | Not run | | BC-06: Load failure | Block sandbox connect script in browser test tools | 1. Reload cart. 2. Inspect available checkout actions. 3. Restore script and reload. | Existing cart/checkout remains accessible; no false payment confirmation; Bolt action recovers after reload. | Not run | ## Payment and order [#payment-and-order] | Test | Input | Steps | Expected output | Result | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------- | | BC-08: Approved payment | Available product; approved Bolt Payments test card | 1. Pay once. 2. Find Bolt transaction. 3. Find store order. | One completed Bolt payment and one matching store order; item, quantity, shopper, amount and currency agree. | Not run | | BC-09: Rejected payment | Pre-auth irreversibly rejected card from the Bolt Payments table, using the card set assigned to your division; fresh cart/link | 1. Submit the rejection card. 2. Inspect transaction and order state. | Payment is rejected before authorization; no order is marked paid; shopper can retry with a supported payment method. | Not run | | BC-10: Cancel checkout | Unpaid cart/link | 1. Open checkout. 2. Close it before paying. 3. Return to the cart/link. | No completed payment; chosen product remains available for another attempt. | Not run | | BC-11: Repeat submit | Fresh test purchase | 1. Submit twice quickly. 2. Reconcile resulting transactions and orders. | No duplicate completed purchase or duplicate paid order. | Not run | | BC-12: Uncertain result | Fresh purchase; controlled connection interruption | 1. Interrupt the browser connection after submit. 2. Restore it. 3. Check Bolt and store before retrying. | Operator can determine the existing outcome; no blind second charge. A completed payment has a matching order. | Not run | ## Experience you control [#experience-you-control] | Test | Input | Steps | Expected output | Result | | ------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------- | | BC-14: Phone and keyboard | Narrow phone and keyboard-only desktop | 1. Reach the checkout entry. 2. Open and close checkout. 3. Return to the entry. | Merchant-owned entry remains usable, visible and reachable; focus and return behavior do not strand the shopper. Report Bolt-owned checkout defects to Bolt. | Not run | | BC-15: Totals | Known product price and supported address | 1. Record store pricing. 2. Enter shipping address. 3. Compare final breakdown. | Product, quantity, shipping, tax, currency and total agree with store configuration. | Not run | ## Additional launch checks [#additional-launch-checks] | Test | Input | Steps | Expected output | Result | | ------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------- | | BC-13: Store identity | Configured logo and support contact | 1. Open checkout. 2. Inspect identity/support. 3. Inspect confirmation. | Correct store identity and contact details; confirmation refers to the purchased product/order. | Not run | | BC-07: Other cart entries | Configured fast cart and mini cart extensions | 1. Apply template reference. 2. Open each entry. 3. Change cart contents and retry. | Every enabled storefront entry reflects its cart. This is outside the cart-page baseline. | Not run | | BC-16: Refund reconciliation | Separate completed sandbox purchase; supported refund setup | 1. Follow the platform refund procedure. 2. Compare Bolt and store records. | Refund amount/status reconcile; no duplicate refund. Record unsupported behavior as a launch blocker, not a passed baseline case. | Not run | | BC-17: Fulfillment | Separate paid order and configured fulfillment workflow | 1. Process the order in the store. 2. Check shopper-facing confirmation/tracking. | Only paid orders enter the intended fulfillment flow; merchant-owned messaging matches the order. | Not run | | BC-18: Production configuration | Approved production account and separate launch checklist | 1. Review hosts/keys/account. 2. Run an approved production-readiness test. | No sandbox keys, links or scripts in production; launch evidence is recorded separately from sandbox acceptance. | Not run |