Hi
As of the introduction of the code coverage feature, none of my tests run anymore.
I just created a sample test, nothing special

file: test_sample.py
`import unittest

class TestSample(unittest.TestCase):
def test_alwaysSucceed(self):
self.assertTrue(True)`

The test is discovered just fine, it shows up, but clicking any of the buttons next to it results in "Finished running tests!" and a timer of 44ms, but no actual outcome, no way to debug it, it seems to not be executing at all, just gets skipped over.
It doesn't matter if I try test itself, or the class, it always does the same thing, maybe the time changes.
The history shows the same, no actual results, just a record of me attempting to run it.

Very confusing, and no idea where to start troubleshooting this issue
Appreciate any help

Thank you
xp

It might be better if you can share the entire project. Would it be possible to share the repo?

Unfortunately I cannot share the project, but I did some digging around and found a few things, and I think I figured it out.
I tried reinstalling just about everything, python, extensions, wsl etc etc, problem kept coming back every time.
I did notice that when I launch code from a windows path ie: C:.... then unitests worked, but I didn't want this, so I went into WSL.
I had a symlink setup to my windows Desktop which pointed to /mnt/c/Users../Desktop where my project lived.
I used code . to start up vscode int that directory, and the issue was back.
I cloned the project to a local WSL directory, ie: /home/user/..../ started up vscode with code . and now everything works.
So it seems that between the two versions something has changed in the way mapping of paths from WSL to windows works, or something with symlinks. Either way, everything else works just fine except for this.

To reproduce, create any project on a windows path, but open it through WSL, and try to run python unittest, seems to only affect windows 10 as I tried the same on win11 and it didn't have the issue.

It seems that i have solved this: the project i tested is stored on a NTFS partition shared by both windows and WSL. In wsl, I created a soft link to it in wsl's virtual file system and opened the project with vscode from the soft link. Under such scenerio the extension would not work with unittest.🙃 If i avoid soft links in the process, i.e. tell vscode to open the workspace located in /mnt/..., the extension would work just fine.