Ladder climb L1->L4: 30 cics-crucible programs below L4, by family (follows #6072)

Abierto
  • ¿Algo no está bien?
#7,434 36 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
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
testing-qa

Línea de trabajo

Start by running ladder_gaps.py on origin/main to get the live list of programs below L4, since the names in the issue are only a starting point. Read the ladder-slice skill and tests/equivalence/infeasible_outcomes.json (with its reasons, per #4602) before adding any case scenarios or reviewed infeasible outcomes. Done means one family's programs reach L4 in a single PR, with before and after net branch coverage stated for each program.

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

Descripción

claim:melek legacy-modernization priority: high scope:core testing

Why

#6072 finished the 74 burned programs it listed (CardDemo, CBSA, GenApp, zECS, DBB). The ladder's remaining work is the cics-crucible programs, which #6072 never listed. This issue is now the focus ladder anchor, and churn's ladder slices run under it.

Numbers from the evidence measure of 2026-11-01T12:31Z, 209 programs: L0 8, L1 11, L2 15, L3 4, L4 151, L5 20. Bar: L3 = 100% paragraph coverage, L4 = 100% net branch coverage (a reviewed infeasible outcome in tests/equivalence/infeasible_outcomes.json, #4602, counts as covered).

L1-L3 -> L4 (30 programs, by family)

  • commarea-mismatch (17): L1 CACCSID, CAGCST, CAGMZ, CALDST, CALDSX, CATWAD, CATWSB, CAXA; L2 CAADDR, CAADSB, CACHSUB, CACHXB, CAEBCA, CAEBSB, CARTWK, CASUB; L3 CALINK
  • condition-handling (6): L1 HCCNSP, HCCWRP, HCRDST; L2 HCEOC, HCEOE, HCSUB
  • ghost-tasks (2): L3 GTREAD, GTRTRN (#7481)
  • pseudo-conversational (5): L2 PCCONF, PCIMMA, PCIMML, PCRCL; L3 PCDETL

Churn re-slices these from each new measure, so these names are a starting point; ladder_gaps.py at origin/main is the live list.

Tracked elsewhere (the 8 programs at L0)

Not translated whole, so not ladder work until their own issue moves them:

  • #6876: CALDTG, HCUNLK, GTHECHO, GTWRECV, GTWSEND
  • #5106: DBB epscsmrd
  • #5866 (named source defects): CardDemo CBEXPORT, CBIMPORT

Known blockers from the last runs

  • HC family: translator DCOUNTER VALUE -> X(8), and an IDCAMS fact (siblings for #6271)
  • HCEOC/HCEOE: terminal device (LUTYPE2) fact in the equivalence harness
  • GTREAD 37:true and GTRTRN 27:true: a harness input for started-task start options (sibling of #6271)

How to slice

One PR per family, as many programs as fit one reviewable PR, data only (case scenarios, reviewed infeasible outcomes with their reason), per the ladder-slice skill. State before/after coverage per program. Burned estates only. Evidence levels, not "proven"; the oracle is GnuCOBOL plus IBM documentation.

Follows #6072.

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

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.