microsoft / microsoft/WinAppVSCE
[vsce-testing] Smoke tests only cover certGenerate; no coverage for pack/debug flows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 3
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 11
Description
Description
The harness's primary smoke test (test-driver-queue.ps1) only validates winapp.certGenerate, but the live campaign depends on winapp.pack, Invoke-VSCodeDriverDebug, and other flows. There is no automated validation that pack/debug work correctly.
Additionally, the editor/intellisense queue step types (queryCompletions, queryHover, queryDefinition, etc.) have no accompanying validation scripts.
Recommendation
- Add a second smoke test covering pack and debug end-to-end
- Add a self-test for the editor/query step types against a known file
Source
Identified during PR review. Pre-existing gaps in the original standalone harness.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with test-driver-queue.ps1 and inspect how it validates winapp.certGenerate. Trace the existing harness entry points for winapp.pack, Invoke-VSCodeDriverDebug, and the editor/query step types. Done means automated validation covers pack/debug flows and self-tests exercise the named query steps against a known file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- cli, developer-experience, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100