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

CI coverage gap: EQUIVALENCE_E2E / CICS_CRUCIBLE_PATH-gated tests never run in any workflow

Abierto
  • ¿Algo no está bien?
#5,954 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, git, java, python
Área
ci-cd, testing

Línea de trabajo

Start by listing tests gated on EQUIVALENCE_E2E and CICS_CRUCIBLE_PATH, then read the Smoke, Mainframe Ground Truth, Full Suite Gate, and cics-crucible runner-tests workflows to compare their environments. Check which gated tests can run in each existing workflow and identify any that can no longer run. Done means every gated test has a workflow that provides its requirements, retired tests are accounted for, and a guard test fails when a gated test is uncovered.

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

Descripción

bug claim:melek priority: high scope:infra testing

Found by a CI test-duplication audit, 2026-10-22 (while working on #5882). Coverage gap, not speed.

Problem: some end-to-end tests never run in any CI workflow, because no workflow sets the variable they need:

  • EQUIVALENCE_E2E is never set for tests/cobol_mainframe. E2E-gated tests there (e.g. test_rounding, test_td_queue_e2e_*, the E2E parts of test_equivalence_cics) are skipped in Smoke, Mainframe Ground Truth and Full Suite Gate alike. Only cics-crucible's runner-tests sets it, and that job runs tests/cics_crucible only.
  • CICS_CRUCIBLE_PATH is never set, so tests/cics_crucible/test_det_port_bytes_4965.py is skipped everywhere, including runner-tests, which does have EQUIVALENCE_E2E=1 and a cics-crucible checkout.

Suggested fix:

  1. List every test gated on EQUIVALENCE_E2E / CICS_CRUCIBLE_PATH and what it needs (Docker GnuCOBOL, JDK + Maven, Db2, the crucible checkout).
  2. Run each in the one workflow that already provides that environment. For example, cics-crucible runner-tests could set CICS_CRUCIBLE_PATH to its checkout.
  3. Retire any that can no longer run.

Then add a guard test that fails if an env-gated test is set up by no workflow, as #5498's matrix test does for shards.

Why it matters: these tests count toward the suite but prove nothing in CI; a regression they cover would land green.

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 20 min
PR fusionados (30 d)
985

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 squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.