Windows import path for unit-tests about vscode-python-test-adapter

[kondratyev-nv]

@LeonOnRoad Thank you for the issue! Can you tell me what is specified in your configuration? Also, it looks like this is more about escaping is Python script

vscode-python-test-adapter/src/unittest/unittestScripts.ts

Line 64 in 7eacfab

return get_tests(loader.discover("${configuration.startDirectory}", pattern="${configuration.pattern}"))

Strings should be treated as raw literals.

[kondratyev-nv]

@LeonOnRoad This issue should be fixed in version 0.3.1. Please, update the extension and let me know if the issue persists.

[LeonOnRoad]

With version 0.3.1 it works fine. Thanks for fixing this!

I couldn't find 'configuration.startDirectory' in any of my configuration, settings or launch json files.
Currently my configuration is Python Current File (Integrated Terminal) (back-end)

Extract from launch.json containing the configuration

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File (Integrated Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        },
...
}

[kondratyev-nv]

I was talking about the unittest argument -s that can be provided in python.unitTest.unittestArgs configuration property in the settings.json file. By default . (current folder) is used.

[LeonOnRoad]

Ok, thanks for clearing that up for me.
Here is my configuration:

"python.unitTest.unittestArgs": [
        "-v",
        "-s", "./tests",
        "-p", "*test*.py"
    ]

This works fine with the python extension when discovering and running tests.