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:

• Reading device or crash logs: ios-android-logs
• Safari Web Inspector / Chrome DevTools debugging: debugging-capacitor
• Build, signing and release pipelines: capacitor-ci-cd
• App Intents tests: capacitor-app-intents (AppIntentsTesting)