ui-tests-migration Skill
Migrate PowerToys module UI tests from the legacy WinAppDriver/Selenium harness (Microsoft.PowerToys.UITest) to the new winappcli-based harness (Microsoft.PowerToys.UITest.Next). Use when asked to port/convert/rewrite/modernize a module's UI tests to the .Next framework, create a new [Module].UITests.Next project along Published by microsoft in PowerToys.
What is ui-tests-migration Skill?
Migrate PowerToys module UI tests from the legacy WinAppDriver/Selenium harness (Microsoft.PowerToys.UITest) to the new winappcli-based harness (Microsoft.PowerToys.UITest.Next). Use when asked to port/convert/rewrite/modernize a module's UI tests to the .Next framework, create a new [Module].UITests.Next project along Published by microsoft in PowerToys. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Design and media
- Browser automation use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use ui-tests-migration Skill
- Use it for browser automation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/PowerToys
- Skill file: .github/skills/ui-tests-migration/SKILL.md
What it does
Migrate PowerToys module UI tests from the legacy WinAppDriver/Selenium harness (Microsoft.PowerToys.UITest) to the new winappcli-based harness (Microsoft.PowerToys.UITest.Next). Use when asked to port/convert/rewrite/modernize a module's UI tests to the .Next framework, create a new [Module].UITests.Next project along
Skill instructions
PowerToys UI-Tests Migration (legacy → .Next) Convert a PowerToys module's UI tests from the legacy WinAppDriver / Selenium / Appium harness (Microsoft.PowerToys.UITest, in src/common/UITestAutomation/) to the new winappcli harness (Microsoft.PowerToys.UITest.Next, in src/common/UITestAutomation.Next/). The new harness shells out to winapp.exe and parses its JSON — no WinAppDriver server on :4723, no Selenium/Appium NuGet packages, no WindowsElement/WindowsDriver. The public shape (UITestBase, Session, Find<T, By, element wrappers like ToggleSwitch) is deliberately similar, so most of the work is mechanical API mapping plus reworking a few patterns that don't translate one-to-one (XPath selectors, stateful elements, instance mouse/keyboard helpers). When to use this skill Use this skill when the task is to: - Port a module's existing legacy UI tests to .Next (e.g. "migrate the ScreenRuler UI tests to the new framework", "convert FancyZones.UITests to winappcli"). - Create a new [Module
Explore related resources
Frequently asked questions
What is ui-tests-migration?
ui-tests-migration is a open-source AI agent skill with Copy skill directory. Migrate PowerToys module UI tests from the legacy WinAppDriver/Selenium harness (Microsoft.PowerToys.UITest) to the new winappcli-based harness (Microsoft.PowerToys.UITest.Next).
Who is ui-tests-migration best for?
ui-tests-migration is best for reusing agent instructions, scripts, and references, browser automation workflows, design and media workflows.
How do I install ui-tests-migration?
Install or run ui-tests-migration using Copy skill directory. Check ui-tests-migration for the latest setup command.
Is ui-tests-migration actively maintained?
ui-tests-migration may need a closer maintenance check before production use.
Auto-fetched from GitHub.
