ci: run molecule-dev smoke tests in CI #16
Reference in New Issue
Block a user
Delete Branch "fix/14-run-smoke-tests-in-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #14.
The repo-owned smoke suite (
tests/test_dev_smoke.py) was documented but never invoked in CI. The existing workflow only ran the canonicalvalidate-plugin.pyand an inline secret scan, so PRs could merge while the smoke tests were effectively skipped.Changes
smokejob to.gitea/workflows/ci.ymlthat installspytest+pyyamland runspython -m pytest tests/ -v.Test plan
python -m pytest tests/ -vpasses locally (26 tests).SOP checklist
smokejob that runs the existing 26 smoke tests; verified locally.pushtomain.Fixes #14
🤖 Generated with Claude Code
APPROVED. 5-axis review complete. Correctness: adds an additive smoke job that runs the repo-owned tests/test_dev_smoke.py suite via python -m pytest tests/ -v, addressing #14 without altering the existing validate job. Robustness: installs pytest and pyyaml explicitly, keeps the canonical validator and inline secret scan intact, and CI / validate plus CI / smoke are success on head
b861a55. Security: no secrets or privileged workflow behavior added; existing secret scan remains unchanged. Performance: bounded 10-minute CI job running the intended smoke tests. Readability: concise workflow addition with clear job naming. No blocking issues found. The separate sop-checklist-gate failure is outside this code review scope.Closing as duplicate of #15, which already adds the same smoke/pytest job to ci.yml and is at the 2-genuine bar (CR2 + Researcher both APPROVED), pending only the org-wide sop-gate token.
Pull request closed