How to execute pytest in a tox environment with the package being in the root directory?

[JackAshwell11]

So if I have a directory structure like this:

proj/
├─ .tox/
├─ package/
│  ├─ source code here
├─ tests/
│  ├─ tests here
├─ pyproject.toml

And my pyproject.toml config:

[tool.pytest.ini_options]
addopts = "-vv -ra --showlocals --cov package --cov-report term-missing"
testpaths = ["tests"]

[tool.tox]
legacy_tox_ini = """
[tox]
envlist = py310
isolated_build = true

[testenv]
allowlist_externals = pytest
deps = pytest-cov
commands =
    python -I -m hades.extensions.compile
    pytest --cov-append
"""

Pytest is running the tests on the source code in package/ instead of the environment inside of .tox. I used to use the src/ directory structure, but since I'm adding Rust extensions, I can't use that anymore.

Is there a way I can get pytest to only run tests on the environments in .tox?

[RonnyPfannschmidt]

Never ever have pytest external

It was pure luck that anything worked at all

You where running tests with a different python/pytest not under tox controls

Allow external is to enable usage of non python executables if necessary, in almost every case it's wrong to use it for stuff pip can install

[JackAshwell11]

Even removing allowlist_externals = pytest still runs the tests on the root directory

[The-Compiler]

I can't see much wrong with what you've shown (other than the allowlist_externals indeed). Could you show the full tox output, as well as whatever it is that you're using to determine where the code is running from?

[JackAshwell11]

Here it is: https://pastebin.com/RWGG4Qa3

I have these C++ extensions that need to be compiled in order for the project to work. Currently, they're not compiled in the root package, but they do get compiled automatically in tox. So if I get an ImportError, I know pytest is running the tests on the root package .since I get an error

[buhtz]

proj/
├─ .tox/
├─ package/
│  ├─ source code here
├─ tests/
│  ├─ tests here
├─ pyproject.toml

I know not much about tox.

How do the you import your packagein the test_*.py files?
Do you manipulate sys.path? This is not recommended.

You should transform your folder structure into src-Layout.
This also implicates that you "install" your package in Development Mode via pip install --editable before you run your tests. I don't know if tox does this for you in the background.

[buhtz]

proj/
├─ .tox/
├─ package/
│  ├─ source code here
├─ tests/
│  ├─ tests here
├─ pyproject.toml

I know not much about tox.

How do the you import your packagein the test_*.py files? Do you manipulate sys.path? This is not recommended.

You should transform your folder structure into src-Layout. This also implicates that you "install" your package in Development Mode via pip install --editable before you run your tests. I don't know if tox does this for you in the background.

The keypoint here is that pytest and your test_*.py files don'T have to take care about where your package is because it is available on every point in your (file) system because of "install" in Development Mode. No need anymore for hacking sys.path. Manipulating sys.path was usual in the past before Python evolved. Today it is "bad practice".