capacitor-testing SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
capacitor-testing from cap-go/capgo-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cap-go/capgo-skills/capacitor-testing@git:20261011.86834d4Pins git:20261011.86834d4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cap-go/capgo-skills
- Path
plugins/capacitor-quality/skills/capacitor-testing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261011.86834d4, committed Oct 11, 2026
- First version recorded
- May 1, 2026
- Size
- 8,142 bytes
- Repository stars
- 74
- License
- MIT
Testing guide for Capacitor apps and plugins. Covers web-layer unit and component tests with Vitest and mocked Capacitor plugins (`vi.mock('@capacitor/core')`, `registerPlugin`), Playwright for the web build, Appium E2E with NATIVE_APP / WEBVIEW context switching, native plugin unit tests with Swift Testing vs XCTest (what can migrate, `CAPPluginCall` patterns, `xcodebuild test` on a simulator) and Android JUnit, plus an agent-driven verification loop on simulators and devices…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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)
## Choose the layer
| What changed | Test with | Reference |
|---|---|---|
| Business logic, state, services that call plugins | Vitest with mocked plugins | [references/web-unit-tests.md](references/web-unit-tests.md) |
…Read the whole file at its exact version.
How to install
mdr add cap-go/capgo-skills/capacitor-testing@sha256:080f297b0f67c523The line at the top of this page pins the label git:20261011.86834d4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_q6sluj3ix4js34co)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 1, 2026 and Oct 11, 2026, about one every 163 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.86834d4 latest | 2026-10-11 | 86834d4 | 8,142 B | A | view · diff |
| git:20260501.ed3e92e | 2026-05-01 | ed3e92e | 14,046 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8142 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cap-go/capgo-skills · 74 stars · license MIT · pushed 2026-10-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q6sluj3ix4js34co GET https://markdownregistry.com/api/v1/resolve?ref=cap-go/capgo-skills/capacitor-testing GET https://markdownregistry.com/api/v1/blob/080f297b0f67c52348d2abae87b820336919b1475c6c403faa8de54eb465fcc1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from cap-go/capgo-skills
Every file in cap-go/capgo-skills