microsoft / microsoft/WinAppVSCE
Test: Add VS Code integration tests for completion/hover provider registration
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 3
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 11
Description
Summary
Add end-to-end VS Code integration coverage for manifest completion and hover provider registration.
Problem
Current tests cover shared IntelliSense logic, but they do not fully verify provider registration and activation wiring inside the VS Code extension host.
Expected
Integration tests should confirm completion and hover providers register correctly, activate under the expected manifest conditions, and remain wired through extension startup/config changes.
Notes
Issue #149 already tracks diagnostics provider lifecycle work; this issue is specifically for completion/hover registration coverage.
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 by locating the existing shared IntelliSense tests, the extension startup and configuration-change wiring, and the VS Code extension-host test entry points. Run the current test suite first. Done means integration coverage confirms completion and hover provider registration, activation under the expected manifest conditions, and continued wiring through startup and configuration changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100