Unit Test discovery executes code found in any `__init__.py` file, causing odd effects.

[LobaDK]

Type: Bug

• Create a folder, with a __init__.py file in it
• Write print('Hello world') in the __init__.py file
• Save (CTRL + S)
• Watch Python Test Log output print Hello world

With a simple print, this is not an issue, but statements that create instances to be used globally, can very quickly cascade. In my case, I am using logging in another class, which I am creating an instance of to be used globally, causing Unit Test Discovery to constantly create a new log file, and logging to it.

Extension version: 2024.14.0
VS Code version: Code 1.93.0 (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 x 2904)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.78GB (20.89GB free)
Process Argv	--crash-reporter-id f3ffeea9-c74b-4d15-952c-c28a1dee7648
Screen Reader	no
VM	50%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl2:31134655
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31134774
wkspc-onlycs-t:31132770
wkspc-ranged-c:31125598
ei213698:31121563

[eleanorjboyd]

Hi! This is done automatically by unittest. If you run unittest from the command line you should see the same behavior and therefore has to do with unittest and not something the extension is doing. Thanks!

[LobaDK]

Running unittest manually through the command line, even with discovery, does not do this. I've never had this issue up until a couple of weeks ago, and had used unittesting way before this started occurring.

Can the automatic unit test discovery that the extension keeps running on every file save be disabled, and if so, how? I really do not see the point of test discovery having to execute every single __init__.py file in my project, creating or overwriting multiple files across it, just to search for unittests. I could understand if I was trying to run the tests, but this happens every single time I hit "save changes", in any file, in the project.

EDIT:
Setting a dedicated path for tests at vscode://settings/python.testing.unittestArgs ended up being the best solution, besides disabling Unittest as a whole in the extension.

[eleanorjboyd]

Hi- you can do the following to stop it running every time a file is saved: "python.testing.autoTestDiscoverOnSaveEnabled": false. Hopefully this will help too!