Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Testing interface is not detecting my .env file #22166

Closed
mayank2gupta opened this issue Sep 19, 2023 · 5 comments
Closed

Testing interface is not detecting my .env file #22166

mayank2gupta opened this issue Sep 19, 2023 · 5 comments
Assignees
@eleanorjboyd
Labels
area-testing bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone
October 2023

Comments

@mayank2gupta
Copy link

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version:
  • OS Version:

Steps to Reproduce:

  1. create the below project structure
    image
  2. set the path of .env file in settings.json file
    image
  3. try to open the testing icon it will give test discovery error due to module not found error, But I have already defined that modules path in .env file and configured it in setttings .json
    image
    image

Meanwhile when I am trying to run it in Integrated terminal it's running absolutely fine

I have tried all the ways possible but I am not able to figure out the issue can someone help me on this
@mayank2gupta
Copy link
Author

@eleanorjboyd can you please work on this

@eleanorjboyd eleanorjboyd mentioned this issue Oct 6, 2023
Merged
@eleanorjboyd eleanorjboyd transferred this issue from microsoft/vscode Oct 6, 2023
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Oct 6, 2023
@eleanorjboyd eleanorjboyd added this to the October 2023 milestone Oct 6, 2023
@eleanorjboyd eleanorjboyd added bug Issue identified by VS Code Team member as probable bug area-testing and removed triage-needed Needs assignment to the proper sub-team labels Oct 6, 2023
eleanorjboyd added a commit that referenced this issue Oct 6, 2023
@eleanorjboyd
fix to get user defined env and use it to set up testing subprocess (#…
e7dfef8 
…22165)

fixes #21642 and
#22166
@eleanorjboyd
Copy link
Member

@mayank2gupta, did the fix I put in work to resolve this?

@eleanorjboyd
Copy link
Member

closing so someone can verify but please comment to reopen.

@eleanorjboyd eleanorjboyd added the verification-needed Verification of issue is requested label Oct 23, 2023
@joaomoreno joaomoreno added verification-steps-needed Steps to verify are needed for verification and removed verification-needed Verification of issue is requested labels Oct 25, 2023
@joaomoreno
Copy link
Member

@eleanorjboyd Please provide simple steps to reproduce the bug and validate the fix.

@DonJayamanne DonJayamanne added the verified Verification succeeded label Oct 25, 2023
@eleanorjboyd eleanorjboyd removed the verification-steps-needed Steps to verify are needed for verification label Oct 26, 2023
@eleanorjboyd
Copy link
Member

Thank you for verifying don, will provide steps in the future!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@eleanorjboyd eleanorjboyd

Labels
area-testing bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Milestone
October 2023
Development

No branches or pull requests
5 participants
@joaomoreno @DonJayamanne @connor4312 @eleanorjboyd @mayank2gupta