test(entrypoint): cover the python -m CLI help path - #147
Conversation
MarcoPorcellato
left a comment
There was a problem hiding this comment.
Hi @MohamedAli1937, thanks for the focused entrypoint test.
One small change is needed before merge: please run the subprocess from tmp_path (for example, cwd=tmp_path). The issue requires the module entrypoint to work independently of the repository working directory, and the current test inherits pytest’s CWD.
Please also add a short timeout to the subprocess, then run make all and push the resulting CI run. Thanks!
|
Done — I rebased onto the latest main, updated the test to use tmp_path and a 10-second timeout, and pushed the changes. CI is running now. |
|
Hi @MohamedAli1937, the checks are green, but GitHub reports conflicts only in generated metrics files. Please rebase on the latest |
a49ec18 to
5d3452d
Compare
Description
Fixes #130
Adds
tests/test_module_entrypoint.pyto verify that executingpython -m logseq_matryca_parser --helpexits cleanly with code 0 and exposes the corematryca-parseCLI surface and subcommands without requiring a user vault.Type of change
🛡️ Sovereign Developer Checklist
CONTRIBUTING.md(or picked a task fromdocs/GOOD_FIRST_ISSUES.md).make alllocally, and all linters (Ruff), type-checkers (Mypy), and tests (Pytest) pass successfully.README.md,docs/,CONTRIBUTING.mdas needed).CHANGELOG.mdunder[Unreleased]for user-visible behavior changes.strict=Trueon domain models).Screenshots / CLI Output (if applicable)