Revenuecat Testing
Use when testing RevenueCat purchases/subscriptions, setting up sandbox testing...
Install
npx skills add evanca/flutter-ai-rules --skill revenuecat-testing -g -a claude-code -y- Repository
- evanca/flutter-ai-rules668
- Category
- Testing
- Updated
- 5d ago
- License
- MIT
- Context cost
- Lightabout 1,425 tokens
- Runs scripts
- No, instructions only
What it does
Use when testing RevenueCat purchases/subscriptions, setting up sandbox testing, debugging a purchase/restore/trial, verifying entitlements or events, checking an app is ready for a RevenueCat experiment, or writing an IAP QA plan.
RevenueCat Testing
Help a developer systematically verify their RevenueCat integration works before shipping, turning "I added RevenueCat, does it actually work?" into a concrete, checkable QA plan. The full use-case matrix, methods, platform differences, and the verifiable signal for each case live in references/use_cases.md. Read it for exact event names and preconditions; this file is the operating guide.
The organizing principle: every RevenueCat behavior has a verifiable signal, a specific dashboard event (INITIAL_PURCHASE, TRANSFER, EXPIRATION, PRODUCT_CHANGE, CANCELLATION), a period_type value, or a CustomerInfo/debug-log state. A test isn't "did the app not crash"; it's "did the expected event appear in the customer's history with the right fields." Always tie a test to its signal, or it isn't really testing anything.
How to use this skill
- Get the setup facts: platform(s) (iOS / Android / cross-platform / web billing), SDK (native, RN, Flutter, etc.), whether they've enabled debug logs and sandbox accounts yet, and what specifically they're trying to verify or why they think something is broken.
- Establish prerequisites first, most "purchases don't work" reports are config problems visible before any purchase:
- Debug logs on before
configure()(iOSPurchases.logLevel = .debug; AndroidsetLogLevel(LogLevel.DEBUG)), and check for "Invalid Product Identifiers" and error-level logs. Fix those before touching purchase flows. - Sandbox environment set up; multiple sandbox test IDs ready if any account-switching is in scope.
- Point them at the debug overlay (
debugRevenueCatOverlay()/DebugRevenueCatBottomSheet) to preview offerings and run test purchases quickly.
- Debug logs on before
- Map their goal to use cases from the reference and produce the plan (below).
