search

kondratyev-nv / vscode-python-test-adapter

Python Test Adapter for the VS Code Test Explorer
https://marketplace.visualstudio.com/items?itemName=LittleFoxTeam.vscode-python-test-adapter
MIT License
117 stars 27 forks source link

select the test case and clilk run, but appeare NOTIFICATIONS: No tests ran #131

Open jxliaocb opened 4 years ago

jxliaocb commented 4 years ago

Issue Type: Bug

select the test case and clilk run, but appeare NOTIFICATIONS: No tests ran, please check the configuration settings for the tests. python2 and 3 has the same issue. Extension version: 0.3.17 VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T15:04:31.999Z) OS version: Linux x64 4.15.0-88-generic

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 x 2394)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|1, 1, 1| |Memory (System)|5.66GB (0.23GB free)| |Process Argv|--no-sandbox --unity-launch| |Screen Reader|no| |VM|100%|
jxliaocb commented 4 years ago

myPY_test_131.tar.gz

in BaseTestCase.py->BasetTestCase->test_1 click test_1 , no case Run.

kondratyev-nv commented 4 years ago

@jxliaocb Thank you for the issue! It looks like your issue is about the Python extension. Most of the tests are successfully ran with the Python Test Adapter. image

But I can reproduce your issue by executing the test with the Python extension. image

Also, you can see that some tests have the message that the test IDs are duplicated. This is the same issue as https://github.com/kondratyev-nv/vscode-python-test-adapter/issues/120. I will try to find the solution, but it looks like this is the default behavior for the unittest framework.