microsoft / microsoft/vscode-test-cli
Testing in isolation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 16
- Avg merge
- 10h 57m
- Merged PRs (30d)
- 2
Description
Feature request
It would be nice to be able to run all tests in isolation.
Ideally, every test would receive a fresh VS Code instance, free of any previous state.
Use case
When running tests that affect the state of VS Code, it can be cumbersome to ensure that some actions have a direct link to a desired state. For example, if you want to test whether opening files of a given type activates the extension, if you run these tests one after the other, the first test will trigger the activation, and subsequent tests will succeed because the previous test has activated the extension.
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
The issue names no files, tests, or entry points. Begin by locating the CLI's test-launch path and any existing isolation-related tests; done means each test receives a fresh VS Code instance without state leaking between tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100