ci: run smoke/pytest suite in plugin CI (#14) #15
Reference in New Issue
Block a user
Delete Branch "ci/add-smoke-tests-14"
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
Problem
The
validatejob ran onlyvalidate-plugin.py+ a secret scan. It did not execute the repo'''s documented smoke suite (tests/test_smoke.py/tests/test_dev_smoke.py), so the artifact-structure assertions in those files never actually ran in CI.Fix
Add a
Run smoke testsstep that invokespython -m pytest tests/ -vafter the existing validate and secret-check steps. Additive — the existing two steps are untouched. The tests are pure unittest; pytest is installed in the step (cached on the runner via pip) only for nicer discovery + summary output. PyYAML is already installed by the existing validate step.Verified locally
Acceptance
Not merged; routing for review per PM directive.
APPROVED. 5-axis review complete. Correctness: adds a real smoke-test step invoking python -m pytest tests/ -v, and the branch contains the repo's actual tests/test_dev_smoke.py suite. Robustness: additive after existing validate and secret-check steps; no weakening of current gates. Security: existing secret scan remains intact. Performance: acceptable CI-only pytest install/test run. Readability: clear step name/comments. No blocking issues found.
5-axis review: APPROVED.
Correctness/robustness: the new
Run smoke testsstep is additive after existing validate and secret scan, installs pytest, and runspython -m pytest tests/ -vagainst the realtests/test_dev_smoke.pysuite. I confirmed the suite contains real manifest, rules, skills, adapter, known-issues, and README assertions and passes directly as unittest locally.Security/performance/readability: no concerns. No existing validation path is weakened; this closes the documented coverage gap.