-
Notifications
You must be signed in to change notification settings - Fork 1.2k
python.testing.cwd
does not work properly
#11669
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.
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
Comments
The below setting is working for me with python unittest
Remember you need to restart your VSCode application after modify your |
This issue is about having |
I don't think having |
@karrtikr what's way you running for test. If using
You also able to using |
I am running the tests directly using play button, not debugging it. |
python.testing.cwd
does not work anymorepython.testing.cwd
does not work properly
python.testing.cwd
does not work properlypython.testing.cwd
does not work properly with .
python.testing.cwd
does not work properly with .
python.testing.cwd
does not work properly
This launchfile doesnt work for me anymore... Do you have the same problem? |
everything works in this issue except: "need to reload window everytime for changes in the setting to take effect". Will create another issue about this specifically but all other aspects of this issue are resolved. |
Uh oh!
There was an error while loading. Please reload this page.
Update setting description saying it only works with absolute paths. Folks often try relative paths which do not work for them Error: spawn <python interpreter> ENOENT on test discovery when
"python.testing.cwd"
is set #15739 (comment).For some reason we need to reload window everytime for changes in the setting to take effect.
It seems the setting doesn't work when using forward slashes in windows:
Have the following test
./Test/test2.py
where.
is workspace folderAnd
./demofile.txt
carrying some random content.Set
python.testing.cwd
to./Test
. Run the file, it doesn't work. Settingpython.testing.cwd
to.\\Test
works.The text was updated successfully, but these errors were encountered: