Test Tauri Apps

Use layered tests. No single test runner proves both the renderer and native shell.

Test Layers

Mock IPC Pattern

import { mockIPC } from "@tauri-apps/api/mocks";

mockIPC((cmd, args) => {
  if (cmd === "load_settings") {
    return { theme: "dark" };
  }

  throw new Error(`unexpected command: ${cmd}`);
});

Use this to keep frontend tests honest about command names and payloads.

Rust Command Tests

Extract validation and business logic into testable functions when command handlers become too coupled to Tauri runtime types.

fn validate_project_id(value: &str) -> bool {
    !value.is_empty() && value.chars().all(|ch| ch.is_ascii_alphanumeric() || ch == '_')
}

#[test]
fn rejects_path_like_project_id() {
    assert!(!validate_project_id("../secret"));
}

WebDriver Smoke

Use WebDriver for a running app smoke path when UI behavior depends on the real shell. The Tauri docs recommend WebdriverIO with the Tauri service and note that direct tauri-driver has platform limits.

Smoke at least:

app launches
main window loads built frontend
one command-backed flow works
one denied/invalid permission path behaves safely
logs contain no secrets
app exits and sidecars clean up

Platform Matrix