PowerShell / PowerShell/vscode-powershell
[Test] Switch to VSCode Extension Runner
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
VSCode now has a specific CLI and test runner extension for vscode E2E tests driven by Mocha
https://code.visualstudio.com/api/working-with-extensions/testing-extension
https://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner
This will move our highly customized testing process to a more standard operation.
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 reviewing the repository's current customized VS Code E2E test process and the linked VS Code extension-testing documentation. The work is done when those tests use the standard VS Code Extension Test Runner rather than the customized process described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100