python -m faircode is never run by a test
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
Research direction
Start with faircode/__main__.py and the CLI tests in tests/test_cli.py; check how the faircode console script is configured in pyproject.toml. Add subprocess coverage for python -m faircode --version and python -m faircode profile --sample --json, checking exit codes and output against faircode.__version__. Done when the module entry point is exercised and its behavior is verified.
Written by the indexing model from the issue text.
Description
Where: faircode/__main__.py, tests/test_cli.py, pyproject.toml (the faircode console script).
Current gap: faircode/__main__.py has 0 percent coverage and no test runs python -m faircode, although it is the invocation the docs and this week's repro commands use. A broken __main__ (a wrong import, a missing sys.exit) or a divergence from the installed faircode console script would not be noticed.
Repro:
$ python3 -m pytest tests -q -m "not slow" --cov=faircode --cov-report=term | grep __main__
faircode/__main__.py 3 3 0%
Suggested approach: a subprocess test that runs python -m faircode --version and python -m faircode profile --sample --json and checks the exit code and output, and asserts the version matches faircode.__version__; optionally run the installed faircode script the same way when it is on the PATH.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 54
Getting set up
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.
More from yakew7/Fair-Code
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 3/5 Half a day Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
internal
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
frostney/GocciaScript#1715 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
review-bot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
midagedev/bloomery#318 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gke-labs/kube-agents#3277 ·
Maintainers usually reply within 1 day
-
bug effort:low model:light plan planner:gpt-6-1-sol tests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day