coveragepy / coveragepy/coveragepy
tests don't run the same way as pytest
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.4k
- Forks
- 525
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 6
Description
Describe the bug
Tests work with pytest but not with coverage run -m pytest
To Reproduce
https://www.travis-ci.org/github/louisabraham/pydivsufsort/jobs/674350015
Additional context
The code doesn't find ".so" files that are supposed to be in the same location as the source file.
The reason is that coverage imports the version in the current folder, not the one in the installation location (I don't know why pytest does that in the first place).
Contributor guide
No contributing guide indexed for this repository
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 reproducing the discrepancy with pytest and coverage run -m pytest, then inspect the Travis job linked in the issue. Trace how the .so files are located when coverage imports the version from the current folder; done means both commands run the tests successfully and resolve the expected files.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100