Log how test discovery and execution is done

Environment data

• VS Code version: 1.24.1
• Extension version (available under the Extensions sidebar): 2018.5.0
• OS and version: Windows 10
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda(Python 3.5)
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
• Relevant/affected Python packages and their versions:

Actual behavior

unittest doesn’t run when selecting ‘Run Current Unit Test File’.

Expected behavior

unittest is ought to run.

Steps to reproduce:

1. Create any unittest case file.
2. Right click inside the file and select ‘Run Current Unit Test File’.

Logs

Output for Python Test Log in the Output panel

start

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

[Extension Host] Error: read ECONNRESET 

settings.json

{
    "python.linting.enabled": false,
    "python.pythonPath": "D:\\path\\to\\conda\\env\\python.exe",
    "python.unitTest.unittestArgs": [
        "-v",
        "-s",
        ".",
        "-p",
        "*test*.py"
    ],
    "python.unitTest.pyTestEnabled": false,
    "python.unitTest.nosetestsEnabled": false,
    "python.unitTest.unittestEnabled": true
}

Alert message: No tests discovered, please check the configuration settings for the tests. No tests ran, please check the configuration settings for the tests.

It was working with VSCode 1.18.1 version, upgraded to the latest version and it doesn’t seem to work to ever since then.

[brettcannon]

I’m leaving this open as we still want to log in the Output what we are doing for test discovery so people can notice that their tests are not being discovered by the test framework and not because of anything the extension is doing.

[luabud]

We’re logging this now, so closing this again 😃