Capacitor Testing

If you're building Capacitor apps and need to test them properly, this covers the full pyramid: unit tests with Vitest, component tests with React Testing Library or Vue Test Utils, E2E tests with Playwright for web and Appium for native. The plugin mocking setup is especially useful since Capacitor's native APIs are a pain to test otherwise. It shows you how to mock everything from basic Capacitor.getPlatform() calls to third-party plugins like biometric auth. The guide assumes you know your way around testing in general and jumps straight into the Capacitor-specific challenges. It's thorough on the web side but the Appium section cuts off, so you'll want other resources for complete native E2E coverage.

skills.sh installs: 1.4K
GitHub stars: 77
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capgo-skills --skill capacitor-testing --agent claude-code

Installs into .claude/skills of the current project.

Files

Testing Capacitor Apps and Plugins

A Capacitor app has three layers to test: the web app (most logic), the native bridge and plugins (Swift/Kotlin), and the running app on a device. Pick the cheapest layer that can catch the bug.

When to Use

TRIGGER when:

Adding unit, component or E2E tests to a Capacitor app
Mocking Capacitor or plugin APIs in Vitest / Jest
Writing or modernizing native unit tests for a plugin (Swift Testing, XCTest, JUnit)
Verifying a change on a simulator, emulator or device ("test this", "does it work", "check on device")
E2E tests that cannot find web elements in the app (WebView context)
Setting up test jobs in CI

Do not use: