Vitest extension does not share with live share
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- developer-experience, testing
Research direction
No source file or test is identified in the issue. First reproduce the missing test controls and output as a guest using the listed Live Share steps; done means guests can view and run tests and see their output in the shared session.
Written by the indexing model from the issue text.
Description
Describe the bug
I cannot view or run tests as a guest in a live share session
Reproduction
Reproduction steps:
- Install test explorer live share and live share extensions
- Start a live share session
- Open the link in a browser which should open a local live share session
- “Trust” the workspace
- You will not see any buttons on the guest live share to run the tests or see any test output
System Info
macOS / vscode
Used Package Manager
npm
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
- Dominant language
- TypeScript
- Stars
- 931
- Forks
- 124
- Avg merge
- 16h 20m
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from vitest-dev/vscode
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vitest-dev/vscode#776 · 1 reaction ·
Maintainers usually reply within 1 day
-
p3-minor-bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
vitest-dev/vscode#823 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
vitest-dev/vscode#822 ·
Maintainers usually reply within 1 day
-
enhancement: pending triage
Difficulty 3/5 1-2 days Newbie friendliness 68/100
vitest-dev/vscode#821 ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 3/5 1-2 days Newbie friendliness 70/100
vitest-dev/vscode#812 ·
Maintainers usually reply within 1 day
All issues in vitest-dev/vscode
Similar issues
-
Table: Space fires onActivate in single-selection mode — the reference doc and the JSDoc disagreeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sidorares/react-x11-components#764 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
backnotprop/plannotator#1840 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JoviDeCroock/pracht#432 ·
Maintainers usually reply within 1 day
-
approved check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Hardware attribute name "app Connection Support" has inconsistent casingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
walletbeat/walletbeat#1628 ·
Maintainers usually reply within 1 day