Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add kci-dev CLI smoke tests to catch Dashboard REST API regressions

Abierto
  • ¿Algo no está bien?
#2,143 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 4 días

@alanpeixinho ya está trabajando en esto.

Desde el 29/9/2026.

  • #2145 de @alanpeixinho — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
api, ci-cd, documentation, testing

Línea de trabajo

Start by identifying the Dashboard CI configuration and the kci-dev CLI workflows that use the REST API, then coordinate with kci-dev maintainers on the supported version and representative commands. Use predictable test data and real API requests, and verify successful command results and useful failure output. Document the local test command, covered version, and update process.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

q4-plan

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.

Lenguaje dominante
Python
Estrellas
10
Forks
32
Merge medio
5 d 8 h
PR fusionados (30 d)
25

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de kernelci/dashboard

Todos los issues de kernelci/dashboard

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.