cavy.app

What It Is

Cavy is an open-source end-to-end testing framework for React Native, designed to help developers quickly write and run UI integration tests for iOS and Android apps. It emphasizes “pure JavaScript”: tests run inside the React Native environment and access components through refs, rather than relying on native accessibility hooks like Appium.

Core Capabilities

Cavy supports organizing tests with describe, it, and beforeEach, and provides helpers such as press, fillIn, focus, pause, exists, containsText, and findComponent for simulating taps, text input, focus actions, and assertions that components exist. It can run with both real devices and simulators, supports iOS and Android, and the setup process is largely consistent across the two platforms. cavy-cli provides commands such as cavy init, run-ios, and run-android, making it suitable for CI integration. It can also output JUnit XML for connecting to test reporting systems. The documentation covers installation, APIs, CLI usage, FAQ, custom helpers, custom reporters, and Native Reporter examples, making it fairly systematic overall.

Pricing and Open Source

The documentation clearly states that Cavy is open-source. Installation is done via yarn or npm, including global installation of cavy-cli and adding cavy as a dev dependency within the project. We did not find any commercial pricing, hosted service, or paid version information. It can therefore be regarded as a free open-source tool, though support appears to rely mainly on the community, GitHub, and Discord.

Pros and Cons

Its advantages are that it is lightweight, easy to get started with, and does not require writing native code, making it especially suitable for existing React Native teams that want to quickly add end-to-end testing. Compared with Detox, the documentation says Cavy offers more consistent iOS/Android installation and supports both real devices and simulators. The drawbacks are also clear: it is JavaScript only, so it cannot cover operations that require native capabilities, such as tapping by screen coordinates. Some components such as Text, TextInput, Touchable, and Pressable need to be wrapped before they can be tested. Expo projects also cannot use the default cavy-cli build flow directly; they need to be built manually and run with --skipbuild.

Who It’s For and Access from China

Cavy is suitable for React Native app teams, mobile QA engineers, and projects that want to run cross-platform UI tests quickly in CI. If stronger native interaction capabilities are needed, Detox or Appium may be worth evaluating. If the goal is only component-level unit testing, Jest is more appropriate. The documentation does not provide information about network access from China, payments, or mirrors, and there is no paid entry point. In practice, usage mainly depends on npm/yarn, GitHub, and Discord, so access stability in mainland China cannot be determined from the documentation alone.