Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#5,954 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, git, java, python
Ambito
ci-cd, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug 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.

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 32m
PR unite (30g)
990

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di squid-protocol/gitgalaxy

Tutte le issue di squid-protocol/gitgalaxy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.