wpf-ui

Automate WPF UI clicks, typing, and screenshot verification via UI Automation.

2|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/shiromac/wpfAutoTester --skill wpf-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wpf-ui
Source: https://github.com/shiromac/wpfAutoTester/tree/main/.claude/skills/wpf-ui
Command: npx skills add https://github.com/shiromac/wpfAutoTester --skill wpf-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many desktop testers and developers must manually inspect WPF application UIs, perform clicks, and enter text to verify behavior; this is slow, error-prone, and hard to reproduce. This Skill streamlines those tasks by providing a repeatable, scriptable way to explore UI controls, interact with elements, and capture screenshots for verification.

Core Features & Use Cases

  • UI Exploration: List windows and control trees (automation_id, name, control_type, visibility) to discover targets for testing.
  • Element Interaction: Perform deterministic click and typing actions using selectors such as automation_id or name+control_type with fallbacks to bounding rectangle clicks.
  • Verification & Capture: Focus windows, take screenshots, and re-list controls or read text to validate outcomes and reproduce issues.
  • Use Case: Automatically scan the Settings window, identify the Save button by automation_id, click it, then capture a screenshot and verify the resulting control state.

Quick Start

Use the wpf-ui skill to inspect the Settings window, list controls, click the Save button, and take a verification screenshot.

Frequently Asked Questions about wpf-ui

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

FAQPage Schema
How do I automate clicks and text input in WPF applications for UI testing?

Automate WPF UI testing by inspecting control trees and performing clicks or text input using selectors like automation_id or name. This provides a repeatable, scriptable way to interact with Windows desktop applications and verify behavior.

Can I capture screenshots during WPF UI automation to verify control state?

Yes, you can capture screenshots during WPF UI automation to verify control state. The process focuses windows, takes screenshots, and re-lists controls to validate outcomes and reproduce issues during testing and debugging.

How do I inspect a WPF control tree to find elements for UI automation?

Inspect WPF control trees by listing windows and controls with attributes like automation_id, name, control_type, and visibility. This UI exploration discovers specific targets for deterministic click and typing actions.

Does WPF UI automation work on Windows 10 and 11 desktop applications?

WPF UI automation works on Windows 10 and 11 desktop WPF applications. It requires access to UI Automation operations to resolve targets, focus windows, and perform interaction actions like clicking and typing.

What is the best way to click a WPF button when the automation_id is unavailable?

When automation_id is unavailable, click WPF buttons using selectors like name and control_type, with fallbacks to bounding rectangle clicks. This ensures deterministic element interaction even without primary identifiers.

Why does my WPF UI automation fail to select the correct control?

WPF UI automation may fail if the target control cannot be resolved by automation_id, name, or bounding rectangle. List the control tree first to verify visibility and ensure the correct selector is used for interaction.