plugin-test

Automate multi-pass acceptance testing for the obsidian-gemini plugin.

515|64|Updated Oct 23, 2024

Search Tags:#automation #testing #documentation #qa #plugin #obsidian #acceptance

Ready to run

npx skills add https://github.com/allenhutchison/obsidian-gemini --skill plugin-test-allenhutchison

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-test
Source: https://github.com/allenhutchison/obsidian-gemini/tree/main/.agents/skills/plugin-test
Command: npx skills add https://github.com/allenhutchison/obsidian-gemini --skill plugin-test-allenhutchison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, multi-phase acceptance testing workflow for the Obsidian Gemini plugin, enabling reliable pre-release validation and artifact generation.

Core Features & Use Cases

Three-pass testing workflow: unit checks, UI/state validations via the Obsidian CLI, and final API-spending verification, all orchestrated to identify regressions early.
Guarded execution and reporting: enforces vault focus guard, phase-by-phase progress reporting, and generates auditable planning and test reports.
Comprehensive coverage: ensures checks across CLI, UI surfaces, and release-report artifacts before shipping.

Quick Start

Run the plugin acceptance test to validate a release candidate against the repository's docs and commands.

Frequently Asked Questions about plugin-test

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

FAQPage Schema

How do I automate acceptance testing for an Obsidian plugin before a release?▼

Automated acceptance testing for an Obsidian plugin is executed through a structured three-pass workflow covering unit checks, UI state validations, and API-spending verification to identify regressions early before release.

What is a three-pass acceptance test workflow for plugin release validation?▼

A three-pass acceptance test workflow sequentially validates unit logic, UI and state behavior via the Obsidian CLI, and final API-spending limits, ensuring comprehensive phase-by-phase regression checks before shipping.

How do I run regression checks across UI state and API limits in Obsidian?▼

Regression checks across UI state and API limits in Obsidian are run by enforcing a guarded vault setup and executing phase-based testing that explicitly reports success or failure for each validation layer.

Does this acceptance testing workflow generate auditable reports for QA documentation?▼

The acceptance testing workflow generates detailed QA documentation by producing auditable planning and test reports with explicit success or failure signals during the phase-by-phase progress reporting.

Can I use this to validate release candidates without manual CLI and UI checks?▼

You can validate release candidates without manual checks by orchestrating a comprehensive automated workflow that enforces vault focus guards and tests CLI surfaces, UI state, and release artifacts.

What are the limitations of automated phase-based testing for Obsidian plugins?▼

Automated phase-based testing for Obsidian plugins is limited to the context of guarded vault execution, relying on the Obsidian CLI for UI state validation and requiring distinct phases for API-spending verification.