Tauri debug testing

Skill Xopoko/plug-n-skills/plugins/tauri/skills/tauri-debug-testing

Ready-to-install skills and plugins for Codex, Claude Code, and AI coding agents: practical workflows for app delivery, architecture, research, design, and agent tooling.

Install

npx -y skills add Xopoko/plug-n-skills --skill tauri-debug-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Debug, test, or stabilize Tauri 2 apps, including Rust compile/runtime errors, frontend API mocks, permissions failures, dev/build mismatches, WebDriver, CI checks, logs, DevTools, and platform-specific test gaps.

SKILL.md

2.6 KB, 582 tokens by cl100k_base, as published. Nobody here has run it

Tauri Debug And Testing

Bundled commands use $PLUGIN_ROOT ($env:PLUGIN_ROOT in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"), otherwise the absolute path of this plugin's root directory.

Use this skill when a Tauri app fails to compile, launch, call native APIs, load frontend assets, pass tests, or behave consistently across dev/build.

Triage Split

Classify the failure before changing code:

Frontend build/test failure.
Rust compile/test failure.
Tauri config or capability failure.
Plugin registration/import mismatch.
Dev server vs packaged static asset mismatch.
Platform WebView or OS dependency issue.
Signing, updater, or distribution issue.

Run:

python3 "$PLUGIN_ROOT/scripts/tauri_project_probe.py" .

Common Checks

cargo check --manifest-path src-tauri/Cargo.toml
cargo test --manifest-path src-tauri/Cargo.toml
pnpm test
pnpm build
pnpm tauri dev
pnpm tauri build

Use the package manager and scripts detected in the repo.

Mocking Frontend Tauri APIs

Use @tauri-apps/api/mocks for frontend unit tests around wrappers:

import { mockIPC, clearMocks } from "@tauri-apps/api/mocks";
import { afterEach, expect, it } from "vitest";
import { invoke } from "@tauri-apps/api/core";

afterEach(() => clearMocks());

it("mocks a command", async () => {
  mockIPC((cmd, args) => {
    if (cmd === "add") return Number(args.a) + Number(args.b);
    throw new Error(`unexpected command: ${cmd}`);
  });

  await expect(invoke("add", { a: 2, b: 3 })).resolves.toBe(5);
});

WebDriver

Use WebDriver when the native shell is part of the risk: windows, dialogs, menus, permissions, packaged launch, or cross-process UI flows. Tauri WebDriver coverage is practical on Linux and Windows; macOS WKWebView has tooling limits, so use other proof there.

Debugging Discipline

Do not fix a missing permission by adding broad capabilities.
Do not ignore Tauri package version mismatches unless official docs and the repo prove the mismatch warning is false.
Capture exact error text and command output. Tauri failures are often caused by one missing config/key/import path.
Verify the same path the user cares about: dev mode, packaged app, CI, or target platform.