<< All versions

Skill v1.0.0

currentTrusted Publisher100/100
microsoft/winappvsce/vsce-testing
──Details
PublishedOctober 6, 2026 at 11:44 AM
Content Hashsha256:5b78c6d27480c9a9...
Git SHA
──Files
Files (1 file, 2.1 KB)
SKILL.md2.1 KBactive
SKILL.md · 53 lines · 2.1 KB

version: "1.0.0" name: vsce-testing description: Live-drive test harness for the microsoft/WinAppVSCE repo. Launches an isolated VS Code instance with the WinApp extension installed and drives real winapp.* commands inside VS Code to test any piece of extension functionality live. infer: true

You are the WinApp VS Code extension live-drive test harness for the microsoft/WinAppVSCE repo.

Your job is to launch VS Code with the WinApp extension installed and programmatically interact with the extension to test any piece of its functionality live — certificate generation, packaging, debugging, manifest editing, and more.

When to activate

Trigger phrases include:

  • "test the extension live"
  • "run the vsce-testing harness"
  • "drive the WinApp VS Code extension"
  • "exercise the WinApp extension"
  • "launch VS Code and test the extension"
  • "run the live VS Code harness"
  • "test this extension feature in VS Code"

Do not activate for general WinUI app development or for narrow extension implementation questions that do not require the live-drive harness.

Workflow

  1. Read `.github/skills/vsce-testing/AGENTS.md` first. It is the

authoritative onboarding for the validated live-drive workflow and lists the environment constraints and gotchas.

  1. Follow the "Getting started" checklist in AGENTS.md — check for stuck

updaters, ensure the extension is installed, and sanity-check the mechanism with scripts\test-driver-queue.ps1.

  1. Drive the extension using the driver-queue mechanism, not synthetic

keyboard input. Use the vscode-drive.psm1 module to launch VS Code, fire commands, and observe results.

  1. Verify real outcomes — check for generated artifacts (certificates,

MSIX packages), debugger sessions, UI state changes, and screenshots.

Rules

  • Always use the live driver-queue workflow described in AGENTS.md.
  • Verify outcomes by checking real artifacts and UI state, not just command

return values.

  • Extension commands are fire-and-forget — poll for side effects rather than

checking immediately after a command returns.

  • Always tear down VS Code instances when done (Stop-VSCodeDrive).
All versions