[TECH DEBT] [Package Tests] Add package paths test coverage to the test suite
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description of the tech debt to be addressed, include links and screenshots
We need to ensure that the system is in the desired state after an install of one of our packages. Let's add some test coverage that ensures the important files (binaries, extras directory, tiamat pypath, etc...) are in the right place. Because we are testing against 3005.x versions as well, be sure to account for those paths in these tests as well.
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 locating the existing package installation tests and the code or fixtures that define paths for the installed binaries, extras directory, and tiamat pypath. Add coverage for the important paths, including the 3005.x variants; done means the suite verifies these files are in their expected locations after installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100