pytest-dev / pytest-dev/pytest
ModuleNotFoundError when passing tests in two directories with similar layouts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
pytest /tmp/component1/tests/integration works.
pytest /tmp/component2/tests/integration works.
pytest /tmp/component1/tests/integration /tmp/component2/tests/integration fails with ModuleNotFoundError for every test module in the component2 directory, eg: ModuleNotFoundError: No module named 'tests.integration.test_xxx'.
Directory layout of each component is like:
component
├── tests
│ └── __init__.py
│ └── integration
│ └── __init__.py
│ └── test_xxx.py
└── src
│ └── main.py
└── setup.py
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the two individual pytest commands and then the combined command against the component1 and component2 layouts described in the issue. Investigate how pytest resolves the tests packages when both integration directories are collected; done means the combined invocation collects and runs test_xxx.py from both components without ModuleNotFoundError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100