obsidian-test-vault-smoke

Validate Obsidian plugin changes via tiered end-to-end smoke tests.

149|8|Updated Jun 17, 2022
One-click install
npx skills add https://github.com/edonyzpc/personal-assistant --skill obsidian-test-vault-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-test-vault-smoke
Source: https://github.com/edonyzpc/personal-assistant/tree/main/.agents/skills/obsidian-test-vault-smoke
Command: npx skills add https://github.com/edonyzpc/personal-assistant --skill obsidian-test-vault-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After making changes to the personal-assistant Obsidian plugin (such as UI updates, Pagelet feature work, Chat or Memory modifications, or packaging changes), standard unit tests and build checks cannot catch regressions that only appear when running inside the actual Obsidian app. This Skill eliminates that gap by providing structured, tiered end-to-end validation workflows for the repo-local test vault.

Core Features & Use Cases

  • Tiered Smoke Testing: Choose the lightest appropriate test tier (quick, app-runtime, full-ui, release-gate) based on the scope of your changes, avoiding wasted effort on overkill checks for small code updates.
  • Obsidian CLI Integration: Run fast runtime validation, DOM state checks, console error capture, and screenshot evidence collection directly via Obsidian's CLI, no manual navigation required.
  • Full UI/UX Validation: Verify visible layout, copy, accessibility, and user workflows (Pagelet review, Chat interaction, Memory prompts, settings) using Computer Use or direct app inspection for release confidence.
  • Use Case: After updating the Pagelet review workflow or fixing a Chat layout bug, run the full-ui smoke tier to confirm the change works as expected for real users before merging or releasing.

Quick Start

Use the obsidian-test-vault-smoke skill to run end-to-end validation of the personal-assistant plugin in the repo-local test vault after UI, runtime, or Pagelet changes.

Frequently Asked Questions about obsidian-test-vault-smoke

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end smoke tests for an Obsidian plugin to catch UI regressions?

To validate Obsidian plugin changes, use tiered smoke testing workflows that execute runtime commands and verify DOM state directly in the app environment. This catches regressions that standard unit tests and build checks cannot detect.

Why do my Obsidian plugin unit tests pass but the app throws runtime errors?

Unit tests cannot catch runtime errors that only appear inside the actual Obsidian app environment. End-to-end validation workflows address this gap by running CLI runtime checks and capturing console errors during real execution.

When do I need to run full UI/UX validation for Obsidian plugin updates?

You need full UI/UX validation for Obsidian plugin updates when modifying Pagelet features, Chat layouts, or Memory prompts. This verifies visible layout, copy, accessibility, and user workflows before merging or releasing.

Does Obsidian CLI integration support automated screenshot evidence capture?

Yes, Obsidian CLI integration supports automated screenshot evidence capture. It runs fast runtime validation, DOM state checks, and console error capture directly via the CLI without requiring manual navigation.

What is the best way to gate an Obsidian plugin release after Pagelet workflow changes?

The best way to gate an Obsidian plugin release after Pagelet workflow changes is running the release-gate smoke tier. This applies full end-to-end verification to confirm changes work for real users before release.

Can I run a quick smoke test for small code updates without overkill checks?

Yes, you can run a quick smoke test tier for small code updates. Tiered smoke testing allows you to choose the lightest appropriate test tier, avoiding wasted effort on overkill checks for minor modifications.