You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Type of virtual environment used (if applicable): venv
Steps to reproduce:
Launch VS code with a python environment configured
Make a test file and run it using the command Python: Run Current Unit Test file in the vscode command console. This will run the test discovery first and then launch your unit tests.
Make a minor change to your unit test file and save it.
Notice that the test discovery runs again, even though you never added a test.
Behavior/suggestion
Unit tests are discovered through nosetests whenever a test file is saved. This triggers a process that takes about 4 seconds for me. Since the tests must be discovered before they can be run, this makes it time consuming to make small changes to a test file.
One suggestion would be to have the option to disable the test discovery when a file is saved, and have an optional command to manually discover unit tests.
It's possible this behavior is coming from src/client/unittests/main.ts:onDocumentSaved, line 69 const tests = await testManager.discoverTests(CommandSource.auto, false, true);
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
This is from the Python Test Logs window:
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
This is probably irrelevant but I'll put it anyways
Environment data
Extension version (available under the Extensions sidebar): `2018.2.1
OS and version:
Python 3.6.3
venv
Steps to reproduce:
Python: Run Current Unit Test file
in the vscode command console. This will run the test discovery first and then launch your unit tests.Behavior/suggestion
Unit tests are discovered through nosetests whenever a test file is saved. This triggers a process that takes about 4 seconds for me. Since the tests must be discovered before they can be run, this makes it time consuming to make small changes to a test file.
One suggestion would be to have the option to disable the test discovery when a file is saved, and have an optional command to manually discover unit tests.
It's possible this behavior is coming from
src/client/unittests/main.ts:onDocumentSaved
, line 69const tests = await testManager.discoverTests(CommandSource.auto, false, true);
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)This is from the Python Test Logs window:
Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)This is probably irrelevant but I'll put it anyways
The text was updated successfully, but these errors were encountered: