microsoft / microsoft/vscode-test
Have a launch.json that uses the downloaded vscode, not the currently running one
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 316
- Forks
- 73
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
The launch configuration for "Run Extension Tests" references ${exeFile}, which is my current vscode, not the one that was downloaded. This should be enhanced to:
- Reference the downloaded one. This could be done with a env variable, a command variable, or a custom debugResolver with a new task type.
- Include the additional params from
getProfileArguments, using the same method
Today I just hardcode these paths into my launch.json but it doesn't work cross-platform.
Contributor guide
No contributing guide indexed for this repository
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 the launch configuration for "Run Extension Tests" and trace how ${exeFile} and getProfileArguments are resolved. Determine how the downloaded VS Code executable and profile arguments should be supplied across platforms, then verify that the configuration launches extension tests without hardcoded paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100