`python.testing.cwd` does not work properly

[karrtikr]

• 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 folder

import unittest   # The test framework

class Test_TestIncrementDecrement1(unittest.TestCase):
    def test_increment(self):
        f = open("./demofile.txt", "r")
        print(f.read())
        self.assertEqual(2, 4)


if __name__ == '__main__':
    unittest.main()

And ./demofile.txt carrying some random content.
Set python.testing.cwd to ./Test. Run the file, it doesn't work. Setting python.testing.cwd to .\\Test works.

[anzvanie]

The below setting is working for me with python unittest

{
    "python.testing.cwd": "path\to\yourworkingdir",
    "python.testing.unittestArgs": [
        "-v",
        "-s",
        ".",
        "-p",
        "test_*.py"
    ],
    "python.testing.unittestEnabled": true,
}

Remember you need to restart your VSCode application after modify your settings.json file.

[karrtikr]

This issue is about having . in python.testing.cwd. Does that work for you?

[anzvanie]

I don't think having . in python.testing.cwd or not is difference.
"python.testing.cwd": ".\\path\to\yourworkingdir" still working for me.

[anzvanie]

@karrtikr what's way you running for test.

If using launch.json file and run directly your file, you need to set working directory manually with cwd property

"configurations": [
	{
		"name": "Python: Current File",
		"type": "python",
		"request": "launch",
		"program": "${file}",
		"console": "integratedTerminal",
		"cwd": "${fileDirname}"
	}
]

You also able to using TEST EXPLORER of VSCode for testing with setting in my previous comment.
But you will be got a problems with TEST EXPLORER of VSCode: run a test case or test class is working normally but debugging will throws an exception Unhandled exception in thread started by.

[karrtikr]

I am running the tests directly using play button, not debugging it.
And that's not how you set debugging which is why it's throwing an error, please see #11587. If that doesn't work I recommend to open up a new issue.