Open a3ng7n opened 2 months ago
+1 getting this too after upgrading my nvim/neotest/neotest-pytest. Can't quite figure out which upgrade caused the regression
+1 getting this too after upgrading my nvim/neotest/neotest-pytest. Can't quite figure out which upgrade caused the regression
Yeah - I was suspecting this could be an issue in neotest proper as well, but just haven't spent enough time to figure out which.
I had this bug on nightly build. when moving to v0.10.0
the bug was gone
I had this bug on nightly build. when moving to
v0.10.0
the bug was gone
is that v0.10.0 of neotest? or neotest-python?
if you're able to do any testing that might help track whether this is a bug in neotest or neotest-python
It seems no tests within files are being discovered - when running file, or running nearest, or debugging nearest the result is "No tests found" from neotest. The test file, however, does show up in the summary window, but shows a "skipped" icon next to it when run.
I created a fresh venv with python 3.12, and installed just pytest 8.3.3, and implemented their getting started:
Running
pytest
yields the following, expected, output:Here's my output of
nvim -v
:And I'm running LazyVim - here's the lazy-lock.json lines for neotest:
and the rest of my configuration is here: https://github.com/a3ng7n/nvim