desktop-test-generation

Generate deterministic Meridian WPF tests for view-model, command, and binding behaviors.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill desktop-test-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-test-generation
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.codex/skills/desktop-test-generation
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill desktop-test-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Desktop changes in a WPF MVVM system can silently break commands, bindings, routing, and state transitions, forcing manual UI verification and slowing refactors.

Core Features & Use Cases

  • Scenario-driven WPF test creation: Generate focused tests for view models, commands, services, shell routes, bindings, dense tables, provider workflows, diagnostics panels, and state transitions.
  • Deterministic and seam-aware coverage: Prefer behavior-level tests that avoid private implementation details, live provider calls, real credentials, and nondeterministic time.
  • Failure and recovery protection: Cover disabled/busy/cancel/retry/empty/error/stale/partial paths so workflow refactors remain safe.

Quick Start

Use the desktop-test-generation skill to create focused tests for the specific Meridian WPF view model and its expected success and failure/recovery behaviors.

Frequently Asked Questions about desktop-test-generation

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

FAQPage Schema
How do I test WPF view model state transitions to prevent silent breaks during refactoring?

Generate focused WPF view model tests covering loading, empty, error, disabled, busy, cancel, retry, success, selected, stale, and partial state scenarios to prevent silent breaks during refactoring. These deterministic tests validate workflow state transitions safely.

What is the best way to unit test WPF command can-execute logic without external dependencies?

Unit test WPF command can-execute logic by generating deterministic tests with fake data and no external dependencies. This approach avoids live provider calls and includes can-execute, async-guard, and cancellation expectations for reliable validation.

How do I cover failure and recovery paths when testing MVVM workflows?

Cover failure and recovery paths in MVVM workflows by generating tests for disabled, busy, cancel, retry, empty, error, stale, and partial states. This ensures workflow refactors remain safe and behavior-level coverage protects against regressions.

Can I test WPF bindings and shell routes without live credentials or real provider calls?

Yes, you can test WPF bindings and shell routes without live credentials or real provider calls. Generate deterministic tests using fake data that avoid nondeterministic time and private implementation details while validating routing behavior.

Does WPF MVVM testing work for dense tables and diagnostics panels?

WPF MVVM testing supports dense tables, diagnostics panels, view models, commands, services, shell routes, and bindings. Generate focused behavior-level tests across the desktop workstation surface to reduce manual UI verification during refactors.