pyronear / pyronear/pyro-engine
Run pyro_camera_api tests in CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The camera-API adapter tests (e.g. pyro_camera_api/tests/test_rest_snapshot.py, added in #382) are not executed by CI. The tests.yml job only runs the top-level tests/ (pyroengine), and pyro_camera_api is a separate package not installed in that env.
Wire pyro_camera_api tests into CI so adapters are covered:
- add a job/step that installs
pyro_camera_apiand runspytestfrom its package root, or - include it in the existing matrix with the right import path.
Context: the REST snapshot adapter landed in #382 with 10 local tests that currently don't gate merges.
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 reading the existing tests.yml job and the package layout under pyro_camera_api. Run pytest from the pyro_camera_api package root to confirm the adapter tests work in that environment. Done means CI installs pyro_camera_api and executes its tests so they gate merges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100