# Test a Capacitor or Ionic app: native shell, web content

> Capacitor and Ionic apps are web pages inside a native shell. How the tester works in the web view, the build to upload, and why a debug build gives more detail.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/test-a-capacitor-or-ionic-app/

## Half native, half web

A Capacitor or Ionic app is a native app whose screens are mostly a web page in a web view, with native plugins for the camera, notifications and storage. Testing it means dealing with both: native prompts and plugins on one side, web content on the other. Tools built for one side often stumble on the other.

## How Testsy handles it

The tester works on the screen the way a person does, so it does not matter to the test whether a button is a native control or an element in a web view. System prompts drawn by the phone (camera, notifications, location) are answered like any other step. Our practice app includes web-view screens for this reason, and our engine tests run on them alongside native ones.

```text
Open the app and sign in with the stored account "customer".
Open Profile and change the display name to "Ada Tester"; save.
When the phone asks for access to photos, allow it, and choose the
first photo as the profile picture.
Check the profile shows "Ada Tester" and the new picture.
Close and reopen the app; check the name is still "Ada Tester".
```

## The build

Capacitor builds are native projects, so the build rules are the same as for any app:

- **Android:** an APK with both arm64-v8a and x86_64 native code, from `./gradlew assembleDebug` or `assembleRelease` in the `android` folder. Our Android devices are emulators of two kinds, so both are needed. [Details](https://testsy.dev/blog/build-an-android-apk-that-runs-on-test-devices/).
- **iOS:** a build for the iOS Simulator, the `.app` zipped, from `xcodebuild -sdk iphonesimulator` on the `ios/App` workspace. [Details](https://testsy.dev/blog/build-an-ios-app-for-testing/).

When a build arrives, the check recognises a Capacitor project and, if the build cannot run, gives the command for it.

## Debug builds show more

From the docs: a release build cannot have its web view contents or console inspected, so a **debug** build gives more detail in the result (the web view's console messages, for example). For day-to-day testing, a debug build is the more useful one; run the release build before you ship.

## Watch for

- Content that loads from your server: the device must reach it, so a `localhost` dev server will not work. Point the build at staging.
- Native plugins that behave differently on a cloud device: the camera has no real lens, for example. Test the flow up to the plugin and the result after it.

This post is part of [Mobile release testing: a guide for app teams](https://testsy.dev/blog/mobile-release-testing-for-app-teams/).
