Test RevenueCat Android integrations using Test Store and mockk.
npx skills add https://github.com/RevenueCat/play-billing-skills --skill testing-revenuecat
Please help me install this Agent Skill. Skill: testing Source: https://github.com/RevenueCat/play-billing-skills/tree/main/revenuecat/testing Command: npx skills add https://github.com/RevenueCat/play-billing-skills --skill testing-revenuecat
This skill addresses the need for a streamlined testing environment for RevenueCat Android integrations, using the Test Store for most scenarios and mockk for unit testing, without relying on the Google Play sandbox for daily iterations.
BillingService interface for unit testing ViewModels and other components without direct interaction with Purchases.Initialize the test environment using the test API key and configure the BillingService for mocking, then run unit tests with the GitHub Actions workflow.
High-intent search queries and answers about installing and using this skill.
Test RevenueCat Android integrations using a Test Store environment and mockk. This setup mimics real-world transaction behaviors, allowing you to bypass the Google Play sandbox for daily development and continuous integration workflows.
The Test Store environment mimics real-world behavior by providing configurable Success, Fail, and Cancel outcomes for transactions, enabling comprehensive unit testing of your billing logic without actual purchases.
You can unit test ViewModels by utilizing a mockable BillingService interface with mockk. This allows you to isolate components and test logic without direct interaction with the Purchases object.
Yes, you can integrate continuous testing using a provided GitHub Actions CI pattern. This allows you to automatically run unit tests on every code push to ensure billing integration stability.
Yes, setting up the test environment requires a RevenueCat Test Store API key. You must initialize the environment with this key and configure the BillingService for mocking before running tests.
While the Test Store handles most scenarios by mimicking real-world behaviors, complex edge cases might still require the actual Google Play sandbox. It is primarily designed to eliminate sandbox dependency for daily iterations.
shahmirerrorConfigure RevenueCat in-app purchases for Expo/React Native apps.
logo-solutionsAutomate CI/CD pipeline setup and enforcement for GitHub Actions workflows.
ahmed3elshaerStandardize Android unit, integration, and UI tests with JUnit5, MockK, Turbine, and Compose testing.
PaddleHQSimulate Paddle transaction flows and webhook events in a sandbox environment.