ImperialCollegeLondon / ImperialCollegeLondon/python-template
`pytest` should be run as CI workflow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Currently the only tests we have are for the patching of the pyproject.toml -- and the test doesn't include the uv option, which is the one we care about -- but if we're going to have tests they should be run as part of the CI workflow.
That said, given that the tests aren't currently useful, let's mark this as on hold for now.
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 reviewing the existing tests for pyproject.toml and how the uv option is handled. Once the tests cover the relevant uv behavior, configure the CI workflow to run pytest; done means the useful tests execute successfully in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100