version unknown

ui-tests-local-vm

microsoft@microsoft⭐ 140.9k stars· last commit 3d ago· 7843 open issues

Run PowerToys UITest.Next suites in persistent Hyper-V VMs over PowerShell Direct. Validate full default and constrained suites on Windows 10 and Windows 11, plus applicable ARM64 guests, then automatically hand implementation tasks to ui-tests-pipeline-ci for commit/push and CI validation. Local green is not end-to-end completion. Use for agentic UI-test iteration, reusable standard-user desktops, payload staging, evidence export, VM customization, clean baselines, or hosts without nested virtualization. Keywords: Hyper-V, local VM, virtual machine, PowerShell Direct, Copy-VMFile, VMBus, checkpoint, unattend, autounattend, ISO, Windows 10 LTSC, Windows 11, ARM64, Windows on ARM, UI tests, UITest.Next, winappcli, TRX, CI handoff.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

7.7/10
Verified
Oct 8, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 140.9k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
7.7/10
📍

Not yet listed on ClawHub or SkillsMP

// README

🔨 Utilities

PowerToys includes over 30 utilities to help you customize and optimize your Windows experience:

📦 Installation

For detailed installation instructions and system requirements, visit the installation docs.

But to get started quickly, choose one of the installation methods below:

Go to the PowerToys GitHub releases, scroll down and select Assets to reveal the installation files, and choose the one that matches your architecture and install scope. For most devices, that would be x64 per-user.

  • User scope installer (default)
winget install Microsoft.PowerToys -s winget
  • Machine-wide scope installer
winget install --scope machine Microsoft.PowerToys -s winget

✨ What's new?

What's new image

To see what's new, check out the release notes.

🛣️ Roadmap

For [v0.103][github-next-release-work], we're working on a new Awake flyout, improving Screen Ruler, and continuing to modernize more utilities with WinUI 3.

❤️ PowerToys Community

The PowerToys team is extremely grateful to have the [support of an amazing active community][community-link]. The

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • .github/skills/ui-tests-local-vm/SKILL.md7.8 KBupstream ↗
    ---
    name: ui-tests-local-vm
    description: "Run PowerToys UITest.Next suites in persistent Hyper-V VMs over PowerShell Direct. Validate full default and constrained suites on Windows 10 and Windows 11, plus applicable ARM64 guests, then automatically hand implementation tasks to ui-tests-pipeline-ci for commit/push and CI validation. Local green is not end-to-end completion. Use for agentic UI-test iteration, reusable standard-user desktops, payload staging, evidence export, VM customization, clean baselines, or hosts without nested virtualization. Keywords: Hyper-V, local VM, virtual machine, PowerShell Direct, Copy-VMFile, VMBus, checkpoint, unattend, autounattend, ISO, Windows 10 LTSC, Windows 11, ARM64, Windows on ARM, UI tests, UITest.Next, winappcli, TRX, CI handoff."
    license: MIT
    ---
    
    # Local VM UI testing
    
    Run PowerToys `.Next` UI tests in a persistent, interactive Windows VM while keeping product and test
    execution off the host. Use this skill as the execution complement to
    [ui-tests-migration](../ui-tests-migration/SKILL.md). Restore the baseline checkpoint or recreate the
    guest when clean-profile behavior must be validated.
    
    The guest is a Hyper-V virtual machine. Nothing runs nested, so the same scaffold works on x64 and on
    Windows on ARM, where nested virtualization is unavailable to any Linux-hosted emulator.
    
    The local correctness gate passes when the **full** suite is green on Windows 10 **and** on
    Windows 11, in two separate VMs. Run Windows 10 Enterprise LTSC 2021 first for the fastest
    feedback, then run the same unfiltered suite on Windows 11. Differences in the shell, compositor,
    theming, and timing break tests that contain nothing Windows 11-specific, and those are exactly
    the failures worth catching locally instead of in CI. On a Windows on ARM host, Windows 11 ARM64
    is the only practical guest; run it with `-Platform ARM64` and get the Windows 10 half from an x64 host.
    
    Start guests with the default resource profile: 4 vCPUs and 8 GB RAM. Get the target suite fully
    green before lowering resources with the `Constrained` profile (1 vCPU and 4 GB RAM).
    
    For **create, migrate, or stabilize** tasks, complete both profiles and then automatically invoke
    [ui-tests-pipeline-ci](../ui-tests-pipeline-ci/SKILL.md): pass its access preflight, commit and push
    the scoped changes, queue CI, and remain attached until terminal validation. **Do not mark the task
    complete at local green or wait for another user request to publish/run CI.** Respect explicit
    local-only/no-push/no-CI scope and the Microsoft FTE/access gates. Local execution or VM setup alone
    does not authorize publication. See the pipeline skill for the shared completion and blocker rules.
    
    ## How the host reaches the guest
    
    | Concern | Mechanism |
    |---|---|
    | Control channel | PowerShell Direct over VMBus. No listener, port, certificate, or firewall rule in the guest. |
    | Bulk payload | `Copy-VMFile` over the Guest Service Interface, ~82 MB/s. The session copy is a fallback and stalls on archives near a gigabyte. |
    | Exchange | Guest-local `C:\PowerToysUiTestExchange\<name>`, mirrored by the controller. The host never shares a folder with the guest. |
    | Host privilege | Hyper-V access: an elevated shell, or an account in the local **Hyper-V Administrators** group. Creating a guest additionally requires real elevation. |
    | Console | `scripts/Get-VmConsoleImage.ps1` renders the framebuffer to PNG, so an agent can read boot and desktop state without VMConnect. |
    
    ## When to use this skill
    
    Use it when asked to:
    
    - Create or migrate UI tests and iterate repeatedly without reprovisioning Windows each run.
    - Validate Explorer, hotkey, WebView2, shell-extension, foreground, or composed-visual behavior in a
      real interactive desktop.
    - Run tests as a true standard user while retaining a separate administrator control channel.
    - Reuse unchanged PowerToys, winappcli, and .NET payloads and refresh only changed archives.
    - Keep a reproducible local VM baseline with optional .NET 10, WebView2, diagnostics, or `msvsmon`.
    - Collect durable `status.json`, TRX, transcripts, logs, screenshots, and failure attachments.
    - Compare revisions in one stable VM before confirming the result from a restored checkpoint.
    
    Do not treat a persistent VM as proof of clean-profile behavior. Caches, registrations, settings, and
    first-run state survive between runs. Restore the baseline checkpoint or recreate the VM when those
    are the behavior under test.
    
    ## Relationship to other UI-test skills
    
    | Skill | Owns |
    |---|---|
    | `ui-tests-migration` | Test design, project scaffolding, framework APIs, assertions, lifecycle, and CI stability. |
    | `ui-tests-local-vm` | Fast persistent-VM setup, deployment, interactive execution, evidence export, and iteration. |
    | `ui-tests-pipeline-ci` | Required post-local commit/push, access preflight, scoped CI, and terminal sign-off for implementation tasks. |
    
    Do not modify stabilized tests merely to make the local VM green. First prove that the suite executes,
    produces assertion-bearing TRX, and has a useful success rate. Classify environment-specific failures
    separately unless the task explicitly asks for stabilization.
    
    ## Guest OS policy
    
    - Two guests, two full suites. Windows 10 Enterprise LTSC 2021 (build 19044/21H2, newer than the
      Windows 10 20H2 baseline) and Windows 11. Both must be fully green before the local gate passes.
      LTSC is not available through Fido; `-Source Fido -Windows 10` automates Microsoft's official
      mobile-user-agent ISO page and is the practical public default. The public ISO/MCT images are too
      old for .NET 10 CET, so Setup Dynamic Update must bring Win10 to 1904x.5007+ before the baseline.
      Use licensed Microsoft subscription media for LTSC when available, and always record the edition,
      ISO hash, and installed full build ([references/setup.md §3](references/setup.md#3-get-windows-media)).
    - Windows 10 runs first: it is the faster loop and surfaces most defects. Windows 11 then runs the
      **same** suite, unfiltered - not only the tests that look Windows 11-specific. A test with no
      Windows 11 content can still fail there, which is the whole reason for the second pass.
    - Narrow filters belong to iteration and diagnosis. They are never the evidence for the Windows 11
      pass.
    - Give each OS its own VM name, `vm.config.psd1`, VHDX, checkpoints, and exchange. Never upgrade or
      repurpose the Windows 10 guest into the Windows 11 guest; the two baselines must stay independent.
    - Surfaces that exist only on Windows 11, such as the tier-1 Explorer context menu, need no special
      handling: the full Windows 11 run already covers them.
    - On a Windows on ARM host, use a Windows 11 ARM64 guest with `-Platform ARM64`. Hyper-V does not
      emulate a foreign architecture, so that host cannot supply the Windows 10 x64 pass - run it on an
      x64 host and report both.
    - A Windows 11 host requirement does not make Windows 11 the first guest target.
    - `-Platform` is not cosmetic: it flows to the guest as the `platform` environment variable, names
      visual baselines, and marks the run as pipeline-like. Use only `x64Win10`, `x64Win11`, or `ARM64`.
    
    ## Required reads
    
    Read only what the task needs:
    
    1. [references/setup.md](references/setup.md) - host requirements, scaffolding, media acquisition,
       unattended guest creation, credentials, standard-user desktop, and checkpoint baselines.
    2. [references/agentic-loop.md](references/agentic-loop.md) - payload contract, controller usage,
       focused-to-suite iteration, evidence, verdicts, and reset strategy.
    3. [references/customization.md](references/customization.md) - persistent image customization,
       .NET 10, WebView2, `msvsmon`, resource profiles, and golden-baseline guidance.
    4. [references/troubleshooting.md](references/troubleshooting.md) - guest creation, PowerShell Direct,
       interactive session, scheduled-task, focus, timeout, and export failures.
    5. [references/shell-extensions-and-signing.md](references/shell-extens
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/microsoft-powertoys-github-skills-ui-tests-local-vm.md

// REPO STATS

140.9k stars
7843 open issues
Last commit: 3d ago