Is your feature request related to a problem? Please describe.
The mactl pipeline run command has no end-to-end tests. Regressions in the run command can go undetected until a user reports a failure in production. The TODO specifically calls out two missing scenarios: normal run and resume from checkpoint.
Describe the solution you'd like
Add E2E tests covering:
- Successful pipeline run with a valid pipeline and project
- Resume from checkpoint using
--checkpoint flag
- Run against a non-existent pipeline (expect a clear error message)
- Run with missing required parameters (expect validation error before API call)
- Run without authentication (expect auth error)
Describe alternatives you've considered
Add integration tests that mock the API server. Faster than full E2E but doesn't catch issues in the API call path or auth layer.
Additional context
See python/michelangelo/cli/mactl/plugins/entity/pipeline/run.py:31. The comment also mentions resume-from-checkpoint as a specific scenario to cover.
Is your feature request related to a problem? Please describe.
The
mactl pipeline runcommand has no end-to-end tests. Regressions in the run command can go undetected until a user reports a failure in production. The TODO specifically calls out two missing scenarios: normal run and resume from checkpoint.Describe the solution you'd like
Add E2E tests covering:
--checkpointflagDescribe alternatives you've considered
Add integration tests that mock the API server. Faster than full E2E but doesn't catch issues in the API call path or auth layer.
Additional context
See
python/michelangelo/cli/mactl/plugins/entity/pipeline/run.py:31. The comment also mentions resume-from-checkpoint as a specific scenario to cover.