Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

environment file and variables don't work

Open
#1,563 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, typescript, vscode
Domain
testing

Research direction

Reproduce the issue with the shown envFile, vmargs, and projectCode setting, then trace how the Java test runner reads the environment file and expands variables. Done means the command contains -DprojectCode=x and the affected tests run with all configured environment variables.

Written by the indexing model from the issue text.

Description

ai-triaged enhancement low-priority test-debugging 
            "envFile": "${workspaceFolder}/.vscode/.env",
            "vmargs": [ 
                "-Xmx512M",
                "-DprojectCode=${env:projectCode}",

there is a projectCode=x line in the .env file so I expect the command to be run to contain -DprojectCode=x instead it gives -DprojectCode= which means my tests don't run.

This happens for every single environment variable I have.

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.