Behavior is different between vscode web and client

Open
#1,647 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, typescript, vscode
Domain
devtools, testing-qa, web-dev

Research direction

Reproduce the Java test run in vscode.dev through a tunnel using the linked demo project, then compare it with the VS Code client flow. Start with project import and the contextLoads() test; done means the web and client versions both import the project and run the test without the workspace-folder error.

Written by the indexing model from the issue text.

Description

ai-triaged bug investigating maven test-execution ui

Recently, when I run java test on web, it showed an errer: Failed to get workspace folder from test item: $(symbol-method) contextLoads().

image

Tunnel Host OS: Linux debian-server 6.1.0-16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12) x86_64 GNU/Linux
Tunnel Host VSCode CLI Version: code 1.85.1 (commit 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2)
Plugin Version: v0.40.1

Client: Microsoft Edge Version 120.0.2210.91 (Official build) (64-bit)

demo project was created by spring initializr without adding any dependency.

How to reduplicate:

  1. Open vscode web and connect to the tunnel.
  2. Open the demo project via direct link, and import the project into workspace. (Also, I don't know why the project wasn't auto imported)
  3. Run contextLoad() test method.

However, when I ran the test method in vscode client, everyting went well.

Client OS: Windows 11 Professional 23H2
Client VSCode Version: 1.85.1 (commit 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2)

  1. Open vscode and connect to the tunnel.
  2. Open the demo project via direct link, and the project will be imported into workspace automatically.
  3. Run contextLoad() test method.

image

I thought the behavior should be the same, but actually not. I have seen some issues #1463 and microsoft/vscode#74104, but I thought these issues were not the same as mine.

Dominant language
TypeScript
Stars
340
Forks
173
Avg merge
1d 2h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-test

All issues in microsoft/vscode-java-test

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.