Plan and evaluate test coverage for e-commerce checkout and Stripe payment flows.
npx skills add https://github.com/cellarwood/figurio --skill test-strategy-cellarwood
Please help me install this Agent Skill. Skill: test-strategy Source: https://github.com/cellarwood/figurio/tree/main/skills/test-strategy Command: npx skills add https://github.com/cellarwood/figurio --skill test-strategy-cellarwood
Prevents regressions and operational risk by defining what to test, how deeply to test it, and when a change is safe to release for Figurio's commerce and fulfillment flows. It focuses on the highest-impact failures that can cause lost revenue, duplicate charges, stranded orders, or broken approval gates.
Create a concise test strategy for a change that touches checkout and preview approval listing scope, highest-risk flows, tests to run, gaps, and a release recommendation.
High-intent search queries and answers about installing and using this skill.
To create a test strategy for Stripe payment flows and checkout state transitions, prioritize high-risk paths like payment intents, webhook replays, and idempotency, then capture order IDs and logs as release gate evidence to prevent duplicate charges or stranded orders.
When modifying e-commerce checkout and preview approval gates, test success paths, duplicate webhook event handling, order-state machine integrity, and at least one operator recovery scenario like refund or rerun to verify safe code changes and fulfillment handoffs.
Release gates verify payment correctness and webhook replay handling by requiring captured evidence such as order IDs, preview approvals, logs, and screenshots that confirm idempotency and state-machine integrity before allowing a release.
Yes, this test planning approach applies to operational recovery workflows in fulfillment by identifying manual operator actions like refunds, reruns, and handoffs, along with the verification steps required to safely recover stranded orders during code changes.
The highest-risk e-commerce failures to cover in a test plan are lost revenue from broken checkout initiation, duplicate charges from improper Stripe payment intent handling, stranded orders from webhook replay failures, and broken preview approval gates.
Yes, this test strategy approach works without external framework dependencies because it functions as a planning and evaluation layer that defines what to test, how deeply to test it, and what evidence to capture for release confidence.
haxlysAutomate Stripe payment workflows for checkout, subscriptions, and webhooks.
cffrankCapture Playwright-based screenshots across devices and create UI evidence reports.
ahtavarasmusForward Stripe webhook events to a local development server.
JFEspanolitoCreate Playwright E2E tests using the Page Object Model.
