vscode-python: tests are not being discovered

So I used you repo, it’s somewhat worked but I got this message (just part of it):

==================================== ERRORS ====================================
___________ ERROR collecting testing3/testfolder2/tests/test_math.py ___________
import file mismatch:
imported module 'test_math' has this __file__ attribute:
  /Users/alan/Downloads/inc_dec_example_repo/testing3/testfolder1/tests/test_math.py
which is not the same as the test file we want to collect:
  /Users/alan/Downloads/inc_dec_example_repo/testing3/testfolder2/tests/test_math.py
HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules
___________ ERROR collecting testing3/testfolder2/tests/test_str.py ____________
import file mismatch:
imported module 'test_str' has this __file__ attribute:
  /Users/alan/Downloads/inc_dec_example_repo/testing3/testfolder1/tests/test_str.py
which is not the same as the test file we want to collect:
  /Users/alan/Downloads/inc_dec_example_repo/testing3/testfolder2/tests/test_str.py
HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules
=========================== short test summary info ============================
ERROR testing3/testfolder2/tests/test_math.py
ERROR testing3/testfolder2/tests/test_str.py
!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!
==================== 55 tests collected, 2 errors in 0.07s =====================

Then I went to my repo. My project settings.json has:

  "python.testing.pytestArgs": ["tests", "-v", "-c", "/dev/null"],
  "python.testing.unittestEnabled": false,
  "python.testing.pytestEnabled": true,

But once I copied your local settings.json something happened, logs showed something, Explorer as well:

your settings.json:

{
  "python.testing.pytestArgs": ["."],
  "python.testing.unittestEnabled": false,
  "python.testing.pytestEnabled": true
}

However, it’s still useless as nothing happens when I click on play test button.

I also use pyproject.toml with

[tool.pytest.ini_options]
addopts = "tests --cov=faceapp --cov-report=term-missing:skip-covered --cov-report=xml -n 8"

But even commenting that line it still have the same problem.

After some try-and-error I found out that your new Test rewrite don’t like "-c", "/dev/null" args in my settings.json

However, this is there to avoid using the set given in pyproject.toml.

Then, I remembered the “symlink” issue and when I used the realpath (even if having a whitespace)… it worked!

Bottomline:

• pyproject.toml is not the issue, I put back my settings for pytest
• remove "-c", "/dev/null" from "python.testing.pytestArgs"
• don’t use symlink
• Please, fix the symlink bug 😄
• Have a nice holidays first

For those using WSL on Windows, the “python.experiments.optOutFrom” will not be supported on your local user settings, you should use the remote user settings. ctrl + shift + p → “Preferences: Open Remote Settings (JSON)”

Oh and one more thing: the output of

conda run -n default --no-capture-output python ~/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.16.0/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear .

appears to list all tests when I run the command myself from the symlink version of the repositories

Can confirm that I have a similar issue as well.

Can you clarify what your setup is with the two root paths? Are those on the same computer?

My file paths look like this:

~/repos/[git-repo-name]

where I have the symlink

repos -> /mnt/data_science/rohana/repos,

~ is /home/rohana1,

and /mnt/data_science is a nfs file share.

Opening any repository from /home/rohana/repos results in no tests being discovered, whereas all tests are discovered when I open any repository from /mnt/data_science/rohana/repos

Running pytest from the terminal works in both places.

Could you try this on the rewrite of the testing infrastructure to see if it occurs here? You can do so by adding this setting to your users settings.json “python.experiments.optInto”: [“pythonTestAdapter”].

Tried doing this, couldn’t figure out how to confirm that the rewrite was working (should Experiment 'pythonTestAdapter' have shown up under OUTPUT > Python?), but it didn’t seem to fix the issue.

System information:

• Linux Rhel-8.7
• VS Code 1.82.2
• python 3.11.5 and 3.10 conda environments
• pytest 7.4.2 and 7.4.0

The same problem with a symlink. Linux (EndeavourOS), vscode 1.82.2, a python 3.11 env managed by the poetry. The unittest can find tests but the pytest cannot. Pytest works well with a realpath