winui-uitest

Debug and stabilize WinUI 3 UI tests for TabNest with WinAppDriver and Appium.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/in0ho1no/TabNest --skill winui-uitest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winui-uitest
Source: https://github.com/in0ho1no/TabNest/tree/main/.claude/skills/winui-uitest
Command: npx skills add https://github.com/in0ho1no/TabNest --skill winui-uitest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create, repair, and run reliable WinUI 3 UI tests for TabNest when WinAppDriver, Appium, AUMID activation, and XAML automation behavior make GUI testing brittle.

Core Features & Use Cases

  • App startup and attachment guidance for WinAppDriver sessions.
  • Reliable handling of context menus, keyboard input, and mouse coordinates in WinUI 3.
  • Practical debugging of AutomationId exposure, settings.json virtualization, and test isolation.
  • Use it when a UI test hangs on activation, a menu item is unreachable, or a control does not appear in the UI Automation tree.

Quick Start

Use this Skill to diagnose a failing TabNest UI test, confirm the app identity and session setup, and apply the correct WinAppDriver interaction strategy.

Frequently Asked Questions about winui-uitest

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

FAQPage Schema
Why does my WinUI 3 UI test hang during app activation with WinAppDriver?

WinUI 3 UI test activation hangs usually stem from invalid AUMID validation or improper WinAppDriver session attachment. Confirming the app identity and applying correct session setup strategies stabilizes app startup and window attachment.

How do I make WinUI 3 context menus and keyboard input reliable for Appium automation?

To make WinUI 3 context menus and keyboard input reliable for Appium automation, apply correct coordinate translation and serialized test execution strategies. This ensures menu items are reachable and input events register correctly within the UI Automation tree.

What is the best way to debug missing controls in the WinUI 3 UI Automation tree?

Debugging missing controls in the WinUI 3 UI Automation tree requires exposing UI Automation-friendly control IDs and validating AutomationId properties. This ensures controls appear correctly and remain accessible to WinAppDriver sessions.

Does WinAppDriver require serialized test execution for WinUI 3 applications?

Yes, WinAppDriver requires serialized test execution for WinUI 3 applications to prevent session conflicts and state pollution. Serialized execution ensures environment-safe settings.json virtualization and maintains test isolation across Appium capabilities.

How do I virtualize settings.json for isolated WinUI 3 UI tests?

To virtualize settings.json for isolated WinUI 3 UI tests, apply environment-safe handling techniques within your Appium capabilities. This prevents test state leakage and ensures each WinAppDriver session operates on a clean configuration.