revenue-scenario-tester

Tests payment, subscription, ad, and analytics flows across 80+ adversarial scenarios.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill revenue-scenario-tester-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenue-scenario-tester
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/revenue-scenario-tester
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill revenue-scenario-tester-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Monetization bugs—failed payments, broken subscription state machines, untracked ad revenue, or missing legal notices—directly cost money and users, but manually testing every revenue path is impractical. This Skill runs end-to-end adversarial testing of all money-related flows and reports exactly which scenarios fail. ## Core Features & Use Cases - Seven Specialized Agents: Payment, Subscription, Ad, Analytics, Store, Security, and KR-Compliance agents each run scenario matrices across Happy/Sad/Bad/Race/Boundary/Permission/State categories, totaling 80+ scenarios. - Auto-Detection and Parallel Execution: Scans the project for Stripe, PortOne, RevenueCat, AdMob, AdSense, GA4, or PostHog, activates only relevant agents, and runs them in parallel via fan-out delegation. - Report and Auto-Fix Loop: Generates a revenue-test-report with PASS/FAIL per scenario, flags critical failures (e.g., unsigned webhooks accepted, missing auto-renewal notices), and optionally runs a RED→GREEN fix-and-retest cycle. - Use Case: After integrating Stripe subscriptions and AdMob ads into an app, ask for a revenue test to verify webhook signature validation, dunning recovery, ad frequency caps, and Korean auto-renewal notice compliance before launch. ## Quick Start Ask the assistant to run revenue scenario tests on this project and generate a pass/fail report for all payment, subscription, and ad flows.

Frequently Asked Questions about revenue-scenario-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test payment and subscription flows end-to-end?

Run the revenue scenario test, which detects your payment provider (Stripe, PortOne, RevenueCat) and executes 35+ scenarios covering successful charges, declined cards, webhook delays, dunning retries, and every subscription state transition. Results are reported per scenario with suggested fixes.

What scenarios does subscription state machine testing cover?

It validates all transitions including trialing to active, active to past_due, past_due recovery, cancellation at period end, resubscribe after cancel, and pause/resume. It also tests race conditions like canceling on renewal day and webhook ordering reversals.

Does it test ad monetization like AdMob or AdSense?

Yes, the Ad Agent runs 10+ scenarios when AdMob or AdSense is detected, covering banner and interstitial display, rewarded ad completion, no-fill failures, frequency caps, and ensuring paying users never see ads.

Can it verify Korean e-commerce legal compliance?

The KR-Compliance Agent checks 8+ requirements including 7-day withdrawal rights, auto-renewal notice sent 7 days before billing, cash receipt issuance, privacy consent, minor payment restrictions, and business information display.

What security attacks does it test against payment systems?

The Security Agent runs adversarial tests including unsigned or replayed webhooks, client-side price tampering, JWT plan field forgery, repeated free-trial abuse, IDOR on other users' subscriptions, and unauthenticated rate-limit checks.

What happens when a revenue test scenario fails?

Failures are listed in the report with expected versus actual behavior and a suggested fix. Critical failures like accepting unsigned webhooks are flagged as launch blockers, and an optional auto-fix loop applies fixes and retests until they pass.