Thank you for your issue report. We are looking into this now! In the meantime, you are likely on the new testing rewrite and this is why you saw a change in behavior. You can opt out of the rewrite as I get this fix in by setting this in your user settings: "python.experiments.optOutFrom": ["pythonTestAdapter"],. If this doesn’t work let me know as this will mean it is a different issue. Thank you and I will send updates in this thread as I get a fix in.

Hi @MaxHorwood, glad it now works! That’s weird it happened unexpectedly but let me know if it resurfaces.

@msonsona glad that upgrade worked as well! Are you not sure about the feasibility at your company you are saying as opposed to just on your own machine? Let me know if you do have any other questions, I am closing this as resolved in the meantime. Thanks!

@msonsona, could you try running pip install --upgrade pytest then running again? We are on pytest 7.4.2 now so I am not sure if there has been changes to this specific hook but that could be an issue.

After upgrading pytest to 7.4.3 (it’s a work-related repo, so not 100% sure about the feasibility of upgrading this on my end, but let’s try for now), I also upgraded to the pre-release version of the extension (now running v2023.19.12981006), and had to remove the folder argument for pytest being set originally in my .vscode/settings.json:

{
    // "python.testing.pytestArgs": [
    //     "repo_test"
    // ],
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "python.testing.pytestPath": "/Users/me/code/repo/env/bin/pytest",
    "git.closeDiffOnOperation": true,
    "python.testing.cwd": "/Users/me/code/repo/repo_test",
    "python.analysis.typeCheckingMode": "off",
    "python.analysis.autoImportCompletions": true
}

and now it seems to be able to discover and run tests!

thanks @eleanorjboyd for your support! 🙌

@msonsona, could you try running pip install --upgrade pytest then running again? We are on pytest 7.4.2 now so I am not sure if there has been changes to this specific hook but that could be an issue.

In terms of a minimal repro this is just a small example project that replicates the bug. If you are happy to share your current project you could send that over so I can try it myself but since some people do not like sharing their whole projects a minimal repro could be a small project you create where you still see the bugs. For example if you create a new workspace, create a simple pytest, and run it does the bug still exist? If so then send over that simple pytest so we are talking about running the same code. Thanks!

@tboddyspargo this should fix your issue: https://github.com/microsoft/vscode-python/pull/22207

hm yes- I am seeing how this would happen. It is written that the test explorer is cleared when the Python subprocess exists with a non-0 exit code which happens when this other issue arises. Will put in a fix for this

I would like to add I’ve been having a similar issue reported here for the past few weeks. Thank you @alimbada for finding a workaround. Installing the Little Fox Team extensions worked without changing any of the VS Code settings.

@eleanorjboyd Reverting to the previous test adapter allows tests to discovered and run correctly within the test explorer (both sidebar and inline), but switching to the new test adapter results in the “0/0 tests passed” issue mentioned by @alimbada. I am running pytest with a Django project, with a few extensions installed.

The ‘OUTPUT’ tab for Python shows (includes redacted lines, happy to send these privately):

2023-08-08 22:16:44.514 [info] Running PYTEST execution for the following test ids: X/X/X.py::XTest::test_X (more tests here, shortened for post)
2023-08-08 22:16:44.515 [info] Server listening on port 49234
2023-08-08 22:16:44.518 [info] Running pytests with arguments: /Users/X/.vscode/extensions/ms-python.python-2023.15.12191008/pythonFiles/vscode_pytest/run_pytest_script.py --rootdir /Users/X/X
2023-08-08 22:16:44.518 [info] > ./X/X/.venv/bin/python ~/.vscode/extensions/ms-python.python-2023.15.12191008/pythonFiles/vscode_pytest/run_pytest_script.py --rootdir .
2023-08-08 22:16:44.518 [info] cwd: ./X/X/
2023-08-08 22:16:52.293 [info] Test server connected to a client.
2023-08-08 22:16:52.334 [info] Test server connected to a client.
2023-08-08 22:16:52.404 [info] Test server connected to a client.
2023-08-08 22:16:52.479 [info] Test server connected to a client.
2023-08-08 22:16:52.526 [info] Test server connected to a client.
2023-08-08 22:16:52.846 [info] Test server connected to a client.
2023-08-08 22:16:52.970 [info] Test server connected to a client.
2023-08-08 22:16:53.064 [info] Client disconnected

The ‘TEST RESULTS’ tab shows:

Finished running tests!

Happy to provide do more tests or provide more information, let me know what you need. I’ve reverted by to the original test adapter for the moment.

Hi @eleanorjboyd,

Thanks for your reply. I’ve actually just got test discovery and debugging working now by changing python.testing.cwd to ${workspaceFolder}/backend instead of just backend. I thought I’d tried this before but maybe the combination of setting python.defaultInterpreterPath to backend/venv/bin/python along with setting python.testing.cwd fixed it. Previously, I was unsure if the ${workspaceFolder} placeholder would work as it did not show up as an autocomplete option when changing that setting but a suggestion from a StackOverflow comment prompted me to try again and this time it worked.

There is one outstanding issue which is that running tests without debugging shows 0/0 tests passed 0.00% in the Test Explorer and shows the following in the output (with one client connection line per test):

2023-08-04 17:20:56.782 [info] > ./backend/venv/bin/python ~/.vscode/extensions/ms-python.python-2023.14.0/pythonFiles/vscode_pytest/run_pytest_script.py --rootdir .
2023-08-04 17:20:56.782 [info] cwd: ./backend
2023-08-04 17:20:57.547 [info] Test server connected to a client.
... <SNIP> ...
2023-08-04 17:20:57.962 [info] Test server connected to a client.
2023-08-04 17:20:57.996 [info] Client disconnected

As mentioned in my previous post, I only need to run tests in VS Code to debug so I’m happy with the current situation as I can still run tests from the terminal and have set up a VS Code task to do so.

However, in the interest of providing more data to improve this extension I applied your suggestion of setting python.experiments.optOutFrom but this did not change the behaviour of running without debugging.