The kci-dev CLI consumes the KernelCI Dashboard REST API. Changes to the API can break CLI commands, even when the Dashboard's own tests pass.
Since kci-dev is a separate project with different maintainers, we need automated compatibility checks to detect these regressions before merging Dashboard changes.
Add a small smoke test suite that runs representative kci-dev commands against the Dashboard API under test. Coordinate with the kci-dev maintainers to select the commands and supported CLI version.
The tests should use predictable test data and exercise actual CLI requests and response handling. Mocked API responses alone would not detect incompatibilities introduced by Dashboard changes.
Acceptance criteria:
- Identify the main CLI workflows that depend on the Dashboard REST API and select a small set for smoke coverage.
- Run the tests against the Dashboard version being checked, including proposed API changes.
- Verify that each selected command completes successfully and produces the expected result.
- Integrate the suite into Dashboard CI so compatibility failures are visible before merging.
- Include enough failure output to identify the affected command and API request.
- Document how to run the tests locally, which kci-dev version they cover, and how to update that version.
Keep the initial scope focused on API compatibility for the selected workflows. Comprehensive CLI testing remains within the kci-dev project's scope.
The kci-dev CLI consumes the KernelCI Dashboard REST API. Changes to the API can break CLI commands, even when the Dashboard's own tests pass.
Since kci-dev is a separate project with different maintainers, we need automated compatibility checks to detect these regressions before merging Dashboard changes.
Add a small smoke test suite that runs representative kci-dev commands against the Dashboard API under test. Coordinate with the kci-dev maintainers to select the commands and supported CLI version.
The tests should use predictable test data and exercise actual CLI requests and response handling. Mocked API responses alone would not detect incompatibilities introduced by Dashboard changes.
Acceptance criteria:
Keep the initial scope focused on API compatibility for the selected workflows. Comprehensive CLI testing remains within the kci-dev project's scope.