Capacitor Testing

This covers the full testing stack for Capacitor apps, from unit tests with Vitest to E2E with Playwright and Appium. You get concrete examples of mocking native plugins like NativeBiometric, platform-specific test utilities, and component testing for both React and Vue. The testing pyramid approach is solid: lots of unit tests for business logic, some integration tests for component interaction, and a few E2E tests for critical flows. What's useful here is the mock setup boilerplate, which is usually the annoying part of testing Capacitor apps. If you're building a mobile app and need more than just "npm test" running a few Jest tests, this gives you the patterns to test across web and native.

skills.sh installs: 216
GitHub stars: 43
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capacitor-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: