Support configurable presentation of project names in test runner
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, testing
Research direction
Start by tracing how the VS Code test runner currently presents Maven and Gradle project names, using the proposed workspace-folder, filesystem-folder, and project-name sources as the requirements. Define the configurable selection or ordering, then verify that projects with different naming sources display the selected value consistently.
Written by the indexing model from the issue text.
Description
When working with vscode workspaces having multiple folders/projects, it would be useful to have more options on how the project names are presented in the test runner. In a complex setup, you might have tens of folders/projects open as the same time with a mixture of gradle and maven projects. Organizations might have repository naming conventions resulting in lengthy names, which makes it challenging to navigate with the current behaviour in the test runner. In addition, maven and gradle project are currently presented differently.
Gradle project without project name defined in settings.gradle:
"project directory name" (might be lengthy in itself)
Gradle project with project name defined in settings.gradle:
"root project name-project directory name" (results in even lenghtier names)
Maven project:
"project artifact id"
Proposed behaviour:
Make it configurable which value should be presented.
- vscode workspace file "folder.name"
- file system folder name (typically same as the repository name)
- maven project name or artifactId / gradle rootProjectName
- a combination of the above
It would be especially nice to be able to choose the vscode workspace folder name, which allows for setting short context specific names.
An alternative is to introduce a default order of selection
- vscode workspace folder name if defined
- maven project name / gradle root project name if defined
- file system folder name
The maven plugin has a similar concept for the format of project node names.
- Dominant language
- TypeScript
- Stars
- 340
- Forks
- 173
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 17
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.
More from microsoft/vscode-java-test
-
ai-triaged bug investigating junit test-discovery test-execution
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/vscode-java-test#1897 · 1 comment ·
-
ai-triaged bug gradle high-priority test-execution
microsoft/vscode-java-test#1880 · 2 comments · 1 assignee ·
-
ai-triaged gradle junit test-execution ux
microsoft/vscode-java-test#1878 · 3 comments · 1 assignee ·
-
ai-triaged enhancement junit low-priority test-execution ui
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-java-test#1836 · 4 comments ·
-
ai-triaged enhancement gradle investigating junit low-priority test-reporting
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-java-test#1824 · 1 comment ·
All issues in microsoft/vscode-java-test
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#13385 · 1 comment ·
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
vangogh
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
knaw-huc/textannoviz#691 ·