connorshea / vscode-ruby-test-adapter

A Ruby test adapter extension for the VS Code Test Explorer
https://marketplace.visualstudio.com/items?itemName=connorshea.vscode-ruby-test-adapter
MIT License
83 stars 50 forks source link

Just a few tests are run #84

Open finnove opened 2 years ago

finnove commented 2 years ago

Issue Type: Bug

When pressing the >> to run all tests, just a few of them (controller tests) are run, and the rest (model, system) are not. When I press the individual arrow for each test it works. If I do this, it works: "testExplorer.useNativeTesting": false

Extension version: 0.9.0 VS Code version: Code 1.60.0 (e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff, 2021-09-01T10:54:53.442Z) OS version: Darwin x64 20.6.0 Restricted Mode: No

System Info |Item|Value| |---|---| |CPUs|Apple M1 (8 x 24)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled| |Load (avg)|2, 2, 2| |Memory (System)|8.00GB (0.04GB free)| |Process Argv|--crash-reporter-id 18f6b910-9121-41f8-9757-950f26044d03| |Screen Reader|no| |VM|0%|
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 pythonvspyt700cf:30270857 pythonvspyt602:30300191 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 pythonvspyt639:30300192 pythontb:30283811 pythonvspyt551:30345470 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 pythondataviewer:30285071 pythonvsuse255:30340121 vscod805:30301674 pythonvspyt200:30340761 vscextlangct:30333562 binariesv615:30325510 vsccppwt:30364497 pythonvssor306:30344512 bridge0708:30335490 pygetstartedc2:30360494 bridge0723:30353136 pythonrunftest32cf:30364560 pythonf5test824:30361777 javagetstartedt:30364666 pythonvspyt187cf:30362783 pydsgsc2:30361791 vscus224:30358039 vssid140cf:30363604 ```
tomdracz commented 2 years ago

Having the same issue here, looks like with native testing mode of Test Explorer there's some weirdness with running all tests. Disabling with "testExplorer.useNativeTesting": false makes the issue go away