crickets-and-comb / crickets-and-comb/reference_package
Fix `pytest` marker warning.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When running tests (with `make full-test` or `make unit` for instance), we see a `PytestUnknownMarkWarning`:
```
../../../../opt/anaconda3/envs/reference_package_py3.12/lib/python3.12/site-packages/_pytest/nodes.py:329
/opt/anaconda3/envs/reference_package_py3.12/lib/python3.12/site-packages/_pytest/nodes.py:329: PytestUnknownMarkWarning: Unknown pytest.mark.e2e - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
marker_ = getattr(MARK_GEN, marker)
../../../../opt/anaconda3/envs/reference_package_py3.12/lib/python3.12/site-packages/_pytest/nodes.py:329
/opt/anaconda3/envs/reference_package_py3.12/lib/python3.12/site-packages/_pytest/nodes.py:329: PytestUnknownMarkWarning: Unknown pytest.mark.integration - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
marker_ = getattr(MARK_GEN, marker)
../../../../opt/anaconda3/envs/reference_package_py3.12/lib/python3.12/site-packages/_pytest/nodes.py:329
/opt/anaconda3/envs/reference_package_py3.12/lib/python3.12/site-packages/_pytest/nodes.py:329: PytestUnknownMarkWarning: Unknown pytest.mark.unit - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
marker_ = getattr(MARK_GEN, marker)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
```
Check out https://docs.pytest.org/en/stable/how-to/mark.html and fix the issue.
Contributor guide
Research direction
Start by running `make full-test` or `make unit` and inspect the pytest configuration used by those commands. Register the `e2e`, `integration`, and `unit` markers as described in the linked pytest documentation, then rerun the commands and confirm the warnings no longer appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100