No test coverage for verifying installers pull in dependencies correctly
Open
Nobody has claimed this yet.
test
- Dominant language
- Python
- Stars
- 128
- Forks
- 110
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 10
Description
Description of issue
Unit tests run against source files of the module in generated folder. System tests are run by building a sdist, which doesn't install the dependencies. This means we don't have test coverage for verifying that the installers pull in dependencies like nitclk, hightime, etc. correctly.
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 reviewing the system tests and the sdist installation path, comparing them with unit tests against the generated folder. Add coverage that builds or installs the sdist and verifies dependencies such as nitclk and hightime are pulled in correctly. Done means installer dependency resolution is exercised by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100